Observed topology
AS20055 AS-WHOLESAIL
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS20055: 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 |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 910 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 796 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 541 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 512 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 410 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 66 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 64 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 64 |
| AS293 | ESnet | Unclassified | IPv4 | 58 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 58 |
Transit
Downstream networks
Networks for which AS20055 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4193 | State of Washington | Unclassified | IPv4 IPv6 | 1,465 |
| AS13370 | Ziply Fiber | Unclassified | IPv4 IPv6 | 1,146 |
| AS3657 | TSS Digital Services | Residential | IPv4 | 688 |
| AS13692 | Douglas FastNet | Residential | IPv4 IPv6 | 612 |
| AS23138 | FIRST STEP INTERNET, LLC | Residential | IPv4 IPv6 | 608 |
| AS23316 | Bel Air Internet, LLC | Residential | IPv4 | 585 |
| AS32522 | Multnomah Education Service District | Unclassified | IPv4 IPv6 | 571 |
| AS31857 | Ziply Fiber | Residential | IPv4 IPv6 | 492 |
| AS18897 | Montana Sky Networks, Inc. | Unclassified | IPv4 IPv6 | 464 |
| AS26128 | 360 Communications, LLC | Unclassified | IPv4 | 456 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20055 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 7,233 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 6,434 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 4,101 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,206 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,781 |
| AS4193 | State of Washington | Unclassified | IPv4 IPv6 | 1,556 |
| AS394345 | Washington State University | Unclassified | IPv4 | 1,420 |
| AS13370 | Ziply Fiber | Unclassified | IPv4 IPv6 | 1,149 |
| AS32522 | Multnomah Education Service District | Unclassified | IPv4 IPv6 | 775 |
| AS13692 | Douglas FastNet | Residential | IPv4 IPv6 | 760 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.