Observed topology
AS6315 XMISSION - XMission, L.C.
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS6315: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,370 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 415 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 112 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 97 |
| AS62494 | UTOPIA | Unclassified | IPv4 IPv6 | 62 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 33 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 33 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 26 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 26 |
| AS293 | ESnet | Unclassified | IPv4 | 25 |
Transit
Downstream networks
Networks for which AS6315 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS401734 | LANtastic Internet | Unclassified | IPv4 IPv6 | 134 |
| AS402028 | Zephyr Broadband, LLC | Unclassified | IPv4 IPv6 | 134 |
| AS53654 | TJF HOLDINGS | Unclassified | IPv4 IPv6 | 120 |
| AS399936 | PBXIO LLC | Unclassified | IPv4 | 101 |
| AS396109 | Yoko Networks Inc. | Unclassified | IPv4 | 63 |
| AS36537 | Bear River Mutual Insurance Company | Unclassified | IPv4 | 58 |
| AS30425 | Utah Transit Authority | Unclassified | IPv4 | 47 |
| AS40761 | Precise Networks, Inc. | Unclassified | IPv4 | 14 |
| AS398987 | PhirePhly Design | Hosting | IPv6 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6315 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,873 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 476 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 155 |
| AS401734 | LANtastic Internet | Unclassified | IPv4 IPv6 | 134 |
| AS402028 | Zephyr Broadband, LLC | Unclassified | IPv4 IPv6 | 134 |
| AS53654 | TJF HOLDINGS | Unclassified | IPv4 IPv6 | 120 |
| AS399936 | PBXIO LLC | Unclassified | IPv4 | 101 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 99 |
| AS396109 | Yoko Networks Inc. | Unclassified | IPv4 | 63 |
| AS62494 | UTOPIA | Unclassified | IPv4 IPv6 | 62 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.