asn.dev

Observed topology

AS29748 QTS-ASH - Quality Technology Services, LLC

Hosting ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29748: 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 IPv61,193
AS1299Arelion Sweden ABTransitIPv4 IPv6235
AS174Cogent Communications, LLCTransitIPv4 IPv698
AS3356Level 3 Parent, LLCTransitIPv4 IPv674
AS11164Internet2EducationIPv424
AS24482SG.GSHostingIPv4 IPv622
AS577Bell CanadaMobileIPv42
AS4637Telstra GlobalUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14632Brown AdvisoryUnclassifiedIPv466
AS40930Meridian Knowledge SolutionsUnclassifiedIPv442
AS19920Akin, Gump, Strauss, Hauer, & FeldUnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,279
AS1299Arelion Sweden ABTransitIPv4 IPv6244
AS174Cogent Communications, LLCTransitIPv4 IPv6102
AS3356Level 3 Parent, LLCTransitIPv4 IPv680
AS14632Brown AdvisoryUnclassifiedIPv466
AS40930Meridian Knowledge SolutionsUnclassifiedIPv442
AS11164Internet2EducationIPv426
AS24482SG.GSHostingIPv4 IPv624
AS577Bell CanadaMobileIPv42
AS4637Telstra GlobalUnclassifiedIPv41

All 11 adjacent →

Provenance

Where this comes from

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