asn.dev

Observed topology

AS54113 FASTLY

Hosting ARIN Content

Upstreams 137 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 122
Adjacent (IPv6) 107
Upstream graph Who carries AS54113, and who carries them, drawn as a map up to the transit-free core. 128 exchanges Where AS54113 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 137

Networks observed carrying traffic for AS54113: 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
AS1299Arelion Sweden ABTransitIPv4 IPv613,179
AS174Cogent Communications, LLCTransitIPv4 IPv68,324
AS3356Level 3 Parent, LLCTransitIPv4 IPv67,120
AS2914NTT America, Inc.TransitIPv4 IPv65,748
AS6939Hurricane Electric LLCTransitIPv4 IPv65,488
AS55836Reliance Jio Infocomm LimitedMobileIPv4 IPv64,900
AS9002RETN LimitedUnclassifiedIPv4 IPv64,155
AS4637Telstra GlobalUnclassifiedIPv4 IPv62,546
AS3257GTT Communications Inc.TransitIPv4 IPv61,566
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv61,368

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS394192Fastly, Inc.UnclassifiedIPv4 IPv62,553

Adjacency

Adjacent networks

All 138

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv613,884
AS174Cogent Communications, LLCTransitIPv4 IPv68,660
AS3356Level 3 Parent, LLCTransitIPv4 IPv67,344
AS2914NTT America, Inc.TransitIPv4 IPv66,095
AS6939Hurricane Electric LLCTransitIPv4 IPv65,799
AS55836Reliance Jio Infocomm LimitedMobileIPv4 IPv64,900
AS9002RETN LimitedUnclassifiedIPv4 IPv64,273
AS4637Telstra GlobalUnclassifiedIPv4 IPv62,620
AS394192Fastly, Inc.UnclassifiedIPv4 IPv62,553
AS3257GTT Communications Inc.TransitIPv4 IPv61,647

Provenance

Where this comes from

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