Observed topology
AS398465 RACKDOG-LLC - Rackdog, LLC
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS398465: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,436 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,994 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,340 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,010 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 982 |
| AS6079 | RCN | Residential | IPv4 IPv6 | 488 |
| AS7029 | Windstream Communications LLC | Residential | IPv4 IPv6 | 441 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 411 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 | 231 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 222 |
Transit
Downstream networks
Networks for which AS398465 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS154395 | Rackdog LLC | Unclassified | IPv4 | 34,810 |
| AS400536 | Nodestop LLC | Unclassified | IPv4 | 2,243 |
| AS400909 | TRAVCHIS, LLC | Unclassified | IPv4 | 1,466 |
| AS397651 | Sneaker Server, LLC | Unclassified | IPv4 IPv6 | 1,454 |
| AS399296 | Rackdog, LLC | Unclassified | IPv4 IPv6 | 1,202 |
| AS9087 | Rackdog, LLC | Hosting | IPv4 | 532 |
| AS211936 | Rackdog, LLC | Unclassified | IPv4 | 480 |
| AS400859 | EXO BROADBAND | Unclassified | IPv4 IPv6 | 384 |
| AS395003 | AB E-Commerce, LLC | Unclassified | IPv4 | 205 |
| AS23511 | Grass DataCo (BVI) Ltd. | Unclassified | IPv4 IPv6 | 191 |
Adjacency
Adjacent networks
Every AS seen directly next to AS398465 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS154395 | Rackdog LLC | Unclassified | IPv4 | 34,810 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 20,039 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 11,285 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 7,112 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 6,087 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,110 |
| AS400536 | Nodestop LLC | Unclassified | IPv4 | 2,243 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,618 |
| AS400909 | TRAVCHIS, LLC | Unclassified | IPv4 | 1,466 |
| AS397651 | Sneaker Server, LLC | Unclassified | IPv4 IPv6 | 1,454 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.