Observed topology
AS13984 SD-DATA-CENTER
Hosting ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS13984: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 427 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 318 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 260 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 239 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 179 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 94 |
| AS396998 | Path Network, Inc. | Unclassified | IPv4 | 59 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 | 49 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 28 |
| AS64073 | Vetta Group | Unclassified | IPv4 IPv6 | 24 |
Transit
Downstream networks
Networks for which AS13984 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS36614 | SD Government | Unclassified | IPv4 | 1,228 |
| AS54238 | Satcom Direct Inc. | Unclassified | IPv4 | 299 |
| AS5702 | Galaxy Networks (division of Kolacom, Inc.) | Unclassified | IPv4 | 177 |
| AS7285 | SageNet LLC | Unclassified | IPv4 | 177 |
| AS11167 | Gogo Business Aviation LLC | Unclassified | IPv4 | 171 |
| AS63183 | Ything LLC | Unclassified | IPv4 IPv6 | 170 |
| AS23137 | Satcom Direct Inc. | Unclassified | IPv4 | 117 |
| AS63031 | Webby Enterprises LLC | Unclassified | IPv4 | 116 |
| AS398737 | IntelliVoice | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS13984 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS36614 | SD Government | Unclassified | IPv4 | 1,228 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,007 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 809 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 720 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 498 |
| AS54238 | Satcom Direct Inc. | Unclassified | IPv4 | 416 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 412 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 278 |
| AS5702 | Galaxy Networks (division of Kolacom, Inc.) | Unclassified | IPv4 | 177 |
| AS7285 | SageNet LLC | Unclassified | IPv4 | 177 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.