asn.dev

Observed topology

AS24115 Equinix

Hosting APNIC Route Server

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24115: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 177

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv44,972
AS18403FPT Telecom CompanyResidentialIPv4369
AS36351IBM CloudHostingIPv4316
AS4648Global-Gateway InternetUnclassifiedIPv4141
AS32787Akamai Technologies, Inc.HostingIPv4116
AS19551Incapsula IncHostingIPv4106
AS18390Spintel Pty LtdResidentialIPv4105
AS56515OXYNET sp. z o.o.UnclassifiedIPv4104
AS35007Miconet Sp. z o.o.ResidentialIPv490
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv472

Adjacency

Adjacent networks

All 208

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

ASNetworkTypeFamiliesPaths seen
AS4608Asia Pacific Network Information CentreUnclassifiedIPv444,712
AS9498BHARTI Airtel Ltd.MobileIPv430,365
AS32787Akamai Technologies, Inc.HostingIPv46,300
AS35280F5 Networks SARLHostingIPv41,496
AS4648Global-Gateway InternetUnclassifiedIPv4788
AS6939Hurricane Electric LLCTransitIPv4762
AS58453China Mobile International LimitedUnclassifiedIPv4566
AS36351IBM CloudHostingIPv4410
AS18403FPT Telecom CompanyResidentialIPv4371
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6354

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.