asn.dev

Observed topology

AS24013 SB - SB Professional Services

Hosting APNIC

Upstreams 11 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 8
Upstream graph Who carries AS24013, and who carries them, drawn as a map up to the transit-free core. 6 exchanges Where AS24013 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS24013: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS3214xTom GmbHHostingIPv4 IPv6102
AS6233xTomHostingIPv4 IPv632
AS4785xTomHostingIPv4 IPv616
AS8888xTom Pty LtdHostingIPv4 IPv616
AS6939Hurricane Electric LLCTransitIPv412
AS3258xTom Japan CorporationHostingIPv44
AS24482SG.GSHostingIPv4 IPv64
AS401753BIXCE IncUnclassifiedIPv4 IPv64
AS56662Marcin GondekUnclassifiedIPv62
AS199854Jens ThiesUnclassifiedIPv62

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS24013 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS24013 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS3214xTom GmbHHostingIPv4 IPv6102
AS6233xTomHostingIPv4 IPv632
AS4785xTomHostingIPv4 IPv616
AS8888xTom Pty LtdHostingIPv4 IPv616
AS6939Hurricane Electric LLCTransitIPv412
AS3258xTom Japan CorporationHostingIPv44
AS24482SG.GSHostingIPv4 IPv64
AS401753BIXCE IncUnclassifiedIPv4 IPv64
AS56662Marcin GondekUnclassifiedIPv62
AS199854Jens ThiesUnclassifiedIPv62

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.