Observed topology
AS577 BACOM
Mobile ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS577: 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 |
|---|---|---|---|---|
| AS1403 | EBOX | Residential | IPv4 IPv6 | 32,452 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 22,191 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 13,529 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 12,598 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 9,020 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 7,805 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 7,698 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 3,833 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 3,312 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 3,297 |
Transit
Downstream networks
Networks for which AS577 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2675 | Shared Services Canada | Unclassified | IPv4 | 15,484 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 11,083 |
| AS855 | Bell Canada | Mobile | IPv4 IPv6 | 7,460 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 7,382 |
| AS35911 | Telebec | Unclassified | IPv4 IPv6 | 6,570 |
| AS6079 | RCN | Residential | IPv4 IPv6 | 5,706 |
| AS3848 | WorldLinx Telecommunications, Inc. | Unclassified | IPv4 IPv6 | 5,265 |
| AS15830 | Equinix (EMEA) Acquisition Enterprises B.V. | Hosting | IPv4 IPv6 | 5,153 |
| AS15321 | Groupe Maskatel | Unclassified | IPv4 | 4,105 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,089 |
Adjacency
Adjacent networks
Every AS seen directly next to AS577 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1403 | EBOX | Residential | IPv4 IPv6 | 2,125,649 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 469,418 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 360,318 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 268,387 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 187,690 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 170,871 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 153,439 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 145,761 |
| AS701 | Verizon Business | Residential | IPv4 IPv6 | 122,946 |
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 80,259 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.