Observed topology
AS21723 GOCO
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS21723: 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 |
|---|---|---|---|---|
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 1,623 |
| AS812 | Rogers Communications Canada Inc. | Mobile | IPv4 IPv6 | 1,481 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,208 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 1,193 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 1,090 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 787 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 693 |
| AS6327 | Shaw Communications | Residential | IPv4 | 361 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 312 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 274 |
Transit
Downstream networks
Networks for which AS21723 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS21724 | GOCO TECHNOLOGY LIMITED PARTNERSHIP | Unclassified | IPv4 | 2,672 |
| AS396313 | MocTel | Unclassified | IPv4 | 165 |
| AS4200633060 | AS4200633060 | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS21723 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS21724 | GOCO TECHNOLOGY LIMITED PARTNERSHIP | Unclassified | IPv4 | 2,672 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,876 |
| AS812 | Rogers Communications Canada Inc. | Mobile | IPv4 IPv6 | 1,846 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 1,731 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 1,680 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 1,673 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 910 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 875 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 400 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 372 |
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.