asn.dev

Observed topology

AS53907 QTS-RIC - Quality Technology Services, LLC

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53907: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6358
AS1299Arelion Sweden ABTransitIPv4 IPv662
AS174Cogent Communications, LLCTransitIPv4 IPv626
AS3356Level 3 Parent, LLCTransitIPv412
AS24482SG.GSHostingIPv4 IPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14454SilverSky, Inc.UnclassifiedIPv41,913
AS53698Ninja-IX CorporationUnclassifiedIPv4 IPv6136
AS22845Virginia Community College SystemEducationIPv4130
AS394987Southern States Cooperative, Inc.UnclassifiedIPv465
AS397039WorldStridesUnclassifiedIPv441

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,099
AS14454SilverSky, Inc.UnclassifiedIPv41,913
AS1299Arelion Sweden ABTransitIPv4 IPv6435
AS174Cogent Communications, LLCTransitIPv4 IPv6184
AS53698Ninja-IX CorporationUnclassifiedIPv4 IPv6137
AS22845Virginia Community College SystemEducationIPv4130
AS394987Southern States Cooperative, Inc.UnclassifiedIPv465
AS397039WorldStridesUnclassifiedIPv441
AS24482SG.GSHostingIPv4 IPv618
AS3356Level 3 Parent, LLCTransitIPv416

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-12 10:00 UTC by route-views2,rrc00, as seen from 75 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.