Observed topology
AS931 AS-HYONIX-US
Hosting ARIN Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS931: 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 |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 9,672 |
| AS20326 | TeraSwitch Networks Inc. | Unclassified | IPv4 IPv6 | 2,153 |
| AS906 | DMIT Cloud Services | Hosting | IPv4 | 1,640 |
| AS917 | Misaka Network, Inc. | Unclassified | IPv4 | 1,534 |
| AS44486 | Oliver Horscht trading as "SYNLINQ" | Unclassified | IPv4 | 549 |
| AS835 | GoCodeIT Inc | Unclassified | IPv4 | 295 |
| AS12129 | 123.Net, Inc. | Hosting | IPv4 | 195 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 168 |
| AS25369 | Hydra Communications Ltd | Hosting | IPv4 | 70 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 59 |
Transit
Downstream networks
Networks for which AS931 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS153325 | Next Era Pte. Ltd. | Unclassified | IPv4 | 1,035 |
| AS917 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 379 |
| AS215081 | Cheuk Wang Wu trading as Zesty Technologies | Unclassified | IPv4 | 318 |
| AS50069 | Misaka Network, Inc. | Hosting | IPv4 IPv6 | 182 |
| AS399114 | Hyonix | Hosting | IPv4 | 121 |
| AS8888 | xTom Pty Ltd | Hosting | IPv4 IPv6 | 96 |
| AS400061 | Hyonix | Unclassified | IPv4 | 62 |
| AS139601 | Krixe Pte. Ltd. | Hosting | IPv6 | 35 |
| AS213122 | Krixe Pte. Ltd. | Unclassified | IPv4 | 16 |
| AS58313 | Misaka Network, Inc. | Unclassified | IPv6 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS931 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 11,656 |
| AS20326 | TeraSwitch Networks Inc. | Unclassified | IPv4 IPv6 | 3,112 |
| AS917 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 2,151 |
| AS906 | DMIT Cloud Services | Hosting | IPv4 | 1,698 |
| AS153325 | Next Era Pte. Ltd. | Unclassified | IPv4 | 1,035 |
| AS8888 | xTom Pty Ltd | Hosting | IPv4 IPv6 | 697 |
| AS44486 | Oliver Horscht trading as "SYNLINQ" | Unclassified | IPv4 | 609 |
| AS215081 | Cheuk Wang Wu trading as Zesty Technologies | Unclassified | IPv4 | 318 |
| AS835 | GoCodeIT Inc | Unclassified | IPv4 | 295 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 197 |
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.