Observed topology
AS6653 VERO-NETWORKS-AS6653
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS6653: 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,439 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 295 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 275 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 244 |
| AS27008 | BendTel | Unclassified | IPv4 | 220 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 128 |
| AS7922 | Comcast Cable Communications, LLC | Residential | IPv4 | 75 |
| AS19108 | Optimum | Unclassified | IPv4 | 57 |
| AS25899 | LS Networks | Unclassified | IPv4 | 40 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 10 |
Transit
Downstream networks
Networks for which AS6653 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS54393 | Fort Lewis College | Unclassified | IPv4 | 813 |
| AS16654 | Vero Broadband | Unclassified | IPv4 | 455 |
| AS33501 | Montana Digital, LLC. | Unclassified | IPv4 IPv6 | 298 |
| AS400126 | Copper Mountain Consolidated Metropolitan District | Unclassified | IPv4 | 195 |
| AS394195 | Clearnetworx | Unclassified | IPv4 | 178 |
| AS18897 | Montana Sky Networks, Inc. | Unclassified | IPv4 | 120 |
| AS20274 | Flathead Valley Community College | Unclassified | IPv4 | 20 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6653 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,762 |
| AS54393 | Fort Lewis College | Unclassified | IPv4 | 813 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 526 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 473 |
| AS16654 | Vero Broadband | Unclassified | IPv4 | 455 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 444 |
| AS33501 | Montana Digital, LLC. | Unclassified | IPv4 IPv6 | 335 |
| AS27008 | BendTel | Unclassified | IPv4 | 220 |
| AS400126 | Copper Mountain Consolidated Metropolitan District | Unclassified | IPv4 | 195 |
| AS394195 | Clearnetworx | Unclassified | IPv4 | 188 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10: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.