Observed topology
AS20326 TERASWITCH - TeraSwitch Networks Inc.
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS20326: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,662 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,114 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 810 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 462 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 394 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 324 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 299 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 175 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 173 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 173 |
Transit
Downstream networks
Networks for which AS20326 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS931 | Hyonix | Hosting | IPv4 IPv6 | 1,236 |
| AS399114 | Hyonix | Hosting | IPv4 | 833 |
| AS213001 | LA5 Digital LTD | Unclassified | IPv4 | 777 |
| AS7859 | pair Networks | Hosting | IPv4 IPv6 | 392 |
| AS3402 | Butterfly Research | Unclassified | IPv4 | 359 |
| AS142594 | SpeedyPage Ltd | Unclassified | IPv4 IPv6 | 263 |
| AS53891 | Zero Position | Unclassified | IPv4 | 177 |
| AS399460 | Helius | Unclassified | IPv4 | 119 |
| AS402722 | Arct | Unclassified | IPv4 | 119 |
| AS35487 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 92 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20326 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,805 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,785 |
| AS931 | Hyonix | Hosting | IPv4 IPv6 | 1,707 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,498 |
| AS213001 | LA5 Digital LTD | Unclassified | IPv4 | 836 |
| AS399114 | Hyonix | Hosting | IPv4 | 833 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 653 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 644 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 498 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 441 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.