Observed topology
AS17378 AS17378 - TierPoint, LLC
Hosting ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS17378: 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 | 7,352 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 6,366 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,635 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,122 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 2,517 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 380 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 255 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 231 |
| AS293 | ESnet | Unclassified | IPv4 | 225 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 201 |
Transit
Downstream networks
Networks for which AS17378 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24459 | RIMU HOSTING LIMITED | Hosting | IPv4 IPv6 | 1,715 |
| AS55045 | TekTonic | Unclassified | IPv4 IPv6 | 860 |
| AS33168 | INLAND IMAGING L.L.C. | Unclassified | IPv4 | 784 |
| AS40476 | Scala Hosting LLC | Hosting | IPv4 | 603 |
| AS36745 | Caleres, Inc. | Unclassified | IPv4 | 480 |
| AS1982 | Northwest Nexus Inc. | Unclassified | IPv4 | 422 |
| AS23357 | -Reserved AS- | Unclassified | IPv4 | 420 |
| AS19107 | Ymax Communications Corp | Unclassified | IPv4 | 360 |
| AS22192 | Pennsylvania State System of Higher Education | Unclassified | IPv4 | 338 |
| AS32373 | AssetWorks, Inc. | Unclassified | IPv4 | 300 |
Adjacency
Adjacent networks
Every AS seen directly next to AS17378 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 12,071 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 9,993 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 5,676 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,823 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 4,165 |
| AS24459 | RIMU HOSTING LIMITED | Hosting | IPv4 IPv6 | 1,715 |
| AS55045 | TekTonic | Unclassified | IPv4 IPv6 | 860 |
| AS33168 | INLAND IMAGING L.L.C. | Unclassified | IPv4 | 784 |
| AS40476 | Scala Hosting LLC | Hosting | IPv4 | 603 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 602 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M 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.