asn.dev

Observed topology

AS40913 QTS-SJC

Hosting ARIN

Upstreams 7 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 3
Upstream graph Who carries AS40913, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS40913 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40913: 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 IPv6388
AS3356Level 3 Parent, LLCTransitIPv4322
AS174Cogent Communications, LLCTransitIPv4 IPv6222
AS6939Hurricane Electric LLCTransitIPv4 IPv6211
AS701Verizon BusinessResidentialIPv438
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv420
AS49915Megaport (UK) LimitedUnclassifiedIPv420

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS394161Tesla Motors, Inc.UnclassifiedIPv4115
AS36432Mirror Plus Technologies Inc.UnclassifiedIPv473

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6456
AS3356Level 3 Parent, LLCTransitIPv4380
AS174Cogent Communications, LLCTransitIPv4 IPv6246
AS6939Hurricane Electric LLCTransitIPv4 IPv6232
AS394161Tesla Motors, Inc.UnclassifiedIPv4115
AS36432Mirror Plus Technologies Inc.UnclassifiedIPv473
AS701Verizon BusinessResidentialIPv446
AS49915Megaport (UK) LimitedUnclassifiedIPv426
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv423

Provenance

Where this comes from

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