Observed topology
AS398704 STACKSINC-BACKBONE - STACKS INC
Unclassified DROP-listed space ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS398704: 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 |
|---|---|---|---|---|
| AS140570 | Hong Kong Beecloud System Technology Services Limited | Hosting | IPv4 IPv6 | 907 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 842 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 216 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 188 |
| AS9286 | KINX | Hosting | IPv4 IPv6 | 169 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 133 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 IPv6 | 132 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 89 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 85 |
| AS7473 | Singapore Telecommunications Ltd | Unclassified | IPv4 IPv6 | 81 |
Transit
Downstream networks
Networks for which AS398704 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS216138 | SKYQUANTUM TELECOM LTD. | Unclassified | IPv4 | 2,044 |
| AS15082 | OMEGAI | Unclassified | IPv4 IPv6 | 193 |
| AS136758 | HONGKONG CENTURY-ONE LIMITED | Unclassified | IPv4 | 182 |
| AS153560 | 202208375N | Unclassified | IPv4 | 117 |
| AS5068 | STACKS INC | Unclassified | IPv4 IPv6 | 88 |
| AS152330 | Alllan Communications Co., Limited | Unclassified | IPv4 | 88 |
| AS131482 | Hangzhou Aron Teconology Co.,Ltd. | Unclassified | IPv4 | 59 |
| AS401254 | NETSOLVE NETWORK TECHNOLOGY LIMITED | Unclassified | IPv4 | 54 |
Adjacency
Adjacent networks
Every AS seen directly next to AS398704 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS216138 | SKYQUANTUM TELECOM LTD. | Unclassified | IPv4 | 2,044 |
| AS138195 | MOACK.Co.LTD | Unclassified | IPv4 | 1,862 |
| AS140570 | Hong Kong Beecloud System Technology Services Limited | Hosting | IPv4 IPv6 | 1,280 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,082 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 339 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 224 |
| AS7473 | Singapore Telecommunications Ltd | Unclassified | IPv4 IPv6 | 193 |
| AS15082 | OMEGAI | Unclassified | IPv4 IPv6 | 193 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 188 |
| AS136758 | HONGKONG CENTURY-ONE LIMITED | Unclassified | IPv4 | 182 |
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.