asn.dev

Observed topology

AS17018 QTS-SAC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17018: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6320
AS1299Arelion Sweden ABTransitIPv4 IPv6306
AS174Cogent Communications, LLCTransitIPv4 IPv6147
AS49915Megaport (UK) LimitedUnclassifiedIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS16816S-Net, Inc.UnclassifiedIPv4 IPv6220
AS53698Ninja-IX CorporationUnclassifiedIPv4 IPv6121
AS36856Mozilla CorporationUnclassifiedIPv4 IPv690
AS54767Restoration Hardware, Inc.UnclassifiedIPv416
AS397045D. Brown ManagementUnclassifiedIPv4 IPv610
AS54695Progent, Corp.UnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6546
AS3356Level 3 Parent, LLCTransitIPv4 IPv6437
AS174Cogent Communications, LLCTransitIPv4 IPv6237
AS16816S-Net, Inc.UnclassifiedIPv4 IPv6220
AS53698Ninja-IX CorporationUnclassifiedIPv4 IPv6121
AS36856Mozilla CorporationUnclassifiedIPv4 IPv690
AS49915Megaport (UK) LimitedUnclassifiedIPv427
AS54767Restoration Hardware, Inc.UnclassifiedIPv416
AS397045D. Brown ManagementUnclassifiedIPv4 IPv610
AS54695Progent, Corp.UnclassifiedIPv44

Provenance

Where this comes from

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