Observed topology
AS6461 ZAYO-6461 - Zayo Bandwidth
Transit DROP-listed space ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS6461: 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,620 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,312 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,175 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 707 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 705 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 696 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 488 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 476 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 466 |
| AS2152 | CENIC | Unclassified | IPv4 | 250 |
Transit
Downstream networks
Networks for which AS6461 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7155 | ViaSat,Inc. | Residential | IPv4 | 155,285 |
| AS46887 | Crown Castle Fiber LLC | Unclassified | IPv4 IPv6 | 55,328 |
| AS30036 | Mediacom Communications Corp | Residential | IPv4 IPv6 | 27,655 |
| AS13977 | Fidium | Residential | IPv4 | 26,512 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 22,872 |
| AS11798 | Ace Data Centers, Inc. | Hosting | IPv4 | 22,156 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 21,844 |
| AS35986 | Vyve Broadband | Unclassified | IPv4 | 19,935 |
| AS11686 | Zayo Bandwidth | Education | IPv4 | 14,648 |
| AS812 | Rogers Communications Canada Inc. | Mobile | IPv4 IPv6 | 11,552 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6461 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 231,199 |
| AS46887 | Crown Castle Fiber LLC | Unclassified | IPv4 IPv6 | 211,953 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 196,171 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 161,780 |
| AS7155 | ViaSat,Inc. | Residential | IPv4 | 159,750 |
| AS2152 | CENIC | Unclassified | IPv4 | 145,094 |
| AS7473 | Singapore Telecommunications Ltd | Unclassified | IPv4 IPv6 | 144,285 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 136,148 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 119,735 |
| AS6424 | EDGOO NETWORKS UNIPESSOAL LDA | Hosting | IPv4 IPv6 | 116,926 |
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.