Observed topology
AS9678 HOSTINGINSIDE HostingInside LTD.
Hosting APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS9678: 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 |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 549 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 378 |
| AS35916 | MULTACOM CORPORATION | Hosting | IPv4 | 117 |
| AS58453 | China Mobile International Limited | Unclassified | IPv4 IPv6 | 89 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 28 |
| AS199524 | G-Core Labs S.A. | Hosting | IPv4 | 27 |
| AS20860 | IOMART CLOUD SERVICES LIMITED | Hosting | IPv4 | 26 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 17 |
| AS38855 | Taiwan Digital Streaming Co. | Unclassified | IPv4 | 15 |
| AS4837 | CHINA UNICOM China169 Backbone | Mobile | IPv4 | 10 |
Transit
Downstream networks
Networks for which AS9678 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209854 | Cyberzone S.A. | VPN | IPv4 | 180 |
| AS152610 | SAELW(TAIWAN) CO., LIMITED | Unclassified | IPv4 IPv6 | 153 |
| AS152624 | UWay Information Technology Inc. | Hosting | IPv4 | 120 |
| AS215294 | Lumina broadband UAB | Unclassified | IPv4 | 120 |
| AS5065 | Bunny Communications | Unclassified | IPv4 | 96 |
| AS30700 | OwO Network, LLC | Hosting | IPv6 | 33 |
| AS63900 | ZUSO Generation Co., Ltd. | Unclassified | IPv4 | 19 |
| AS34939 | NextDNS, Inc. | Hosting | IPv4 IPv6 | 11 |
| AS203391 | Cloud DNS Ltd | Hosting | IPv4 | 6 |
| AS52025 | ParadoxNetworks Limited | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9678 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 890 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 688 |
| AS209854 | Cyberzone S.A. | VPN | IPv4 | 180 |
| AS152610 | SAELW(TAIWAN) CO., LIMITED | Unclassified | IPv4 IPv6 | 153 |
| AS58453 | China Mobile International Limited | Unclassified | IPv4 IPv6 | 129 |
| AS152624 | UWay Information Technology Inc. | Hosting | IPv4 | 120 |
| AS215294 | Lumina broadband UAB | Unclassified | IPv4 | 120 |
| AS35916 | MULTACOM CORPORATION | Hosting | IPv4 | 117 |
| AS5065 | Bunny Communications | Unclassified | IPv4 | 96 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 43 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.