Observed topology
AS19256 COMMNET-WIRELESS-LLC
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS19256: 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,100 |
| AS7385 | Allstream Business US, LLC | Unclassified | IPv4 IPv6 | 425 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 236 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 221 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 65 |
| AS20228 | Navajo Tribal Utility Authority | Unclassified | IPv6 | 33 |
Transit
Downstream networks
Networks for which AS19256 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS19256 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,340 |
| AS7385 | Allstream Business US, LLC | Unclassified | IPv4 IPv6 | 425 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 265 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 225 |
| AS401350 | Conexon Connect | Unclassified | IPv4 IPv6 | 101 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 65 |
| AS27403 | Apache County Board of Supervisors | Unclassified | IPv4 | 65 |
| AS32021 | Oso Internet Solutions | Unclassified | IPv4 | 53 |
| AS402160 | Truth or Consequences Municipal Schools | Unclassified | IPv4 | 44 |
| AS20228 | Navajo Tribal Utility Authority | Unclassified | IPv6 | 33 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 16:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.19M 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.