Observed topology
AS20394 MASHELL-TELECOM
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS20394: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 171 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 123 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 97 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 6 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 5 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 5 |
| AS52025 | ParadoxNetworks Limited | Unclassified | IPv4 | 3 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS20394 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS14677 | City of Tacoma | Unclassified | IPv4 | 4,253 |
| AS12175 | Rainier Connect | Unclassified | IPv4 | 1,181 |
| AS55214 | Coast Communications Company | Unclassified | IPv4 | 295 |
| AS396001 | City of Tacoma | Unclassified | IPv4 | 265 |
| AS393746 | Amazing Creations and More LLC | Unclassified | IPv4 | 118 |
| AS54256 | Velocity Communications Inc. | Unclassified | IPv4 IPv6 | 84 |
| AS21613 | Quinault Indian Nation | Unclassified | IPv4 | 59 |
| AS40367 | Harbor Regional Health Community Hospital | Unclassified | IPv4 | 43 |
| AS62894 | Puyallup School District | Unclassified | IPv4 | 18 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20394 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS14677 | City of Tacoma | Unclassified | IPv4 | 4,312 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,832 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 2,378 |
| AS12175 | Rainier Connect | Unclassified | IPv4 | 1,181 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 851 |
| AS55214 | Coast Communications Company | Unclassified | IPv4 | 295 |
| AS396001 | City of Tacoma | Unclassified | IPv4 | 265 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 223 |
| AS393746 | Amazing Creations and More LLC | Unclassified | IPv4 | 177 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 119 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.