Observed topology
AS9416 MULTIMEDIA-AS-AP Hoshin Multimedia Center Inc.
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS9416: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,819 |
| AS9505 | Taiwan Internet Gateway | Unclassified | IPv4 IPv6 | 575 |
| AS15412 | Flag Telecom UK Limited | Unclassified | IPv4 IPv6 | 466 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 67 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 56 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 | 36 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 4 |
| AS216458 | Hardcore Communication Co., Limited | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS9416 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS38851 | TNET Communication Inc. 10F., No.78, Sec. 2, Chongxin Rd., Sanchong Dist.,New Taipei City, Taiwan (R.O.C Taiwan 241) | Residential | IPv4 | 732 |
| AS18042 | Koos Broadband Telecom | Unclassified | IPv4 IPv6 | 432 |
| AS17809 | VEE TIME CORP. | Residential | IPv4 | 275 |
| AS14789 | Cloudflare, Inc. | Unclassified | IPv4 IPv6 | 102 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9416 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,863 |
| AS9505 | Taiwan Internet Gateway | Unclassified | IPv4 IPv6 | 801 |
| AS15412 | Flag Telecom UK Limited | Unclassified | IPv4 IPv6 | 773 |
| AS38851 | TNET Communication Inc. 10F., No.78, Sec. 2, Chongxin Rd., Sanchong Dist.,New Taipei City, Taiwan (R.O.C Taiwan 241) | Residential | IPv4 | 732 |
| AS18042 | Koos Broadband Telecom | Unclassified | IPv4 IPv6 | 498 |
| AS17809 | VEE TIME CORP. | Residential | IPv4 | 275 |
| AS14789 | Cloudflare, Inc. | Unclassified | IPv4 IPv6 | 102 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 83 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 67 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 | 36 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.