Observed topology
AS4842 TH-AS-AP Tianhai InfoTech
Hosting APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS4842: 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.
Transit
Downstream networks
Networks for which AS4842 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24239 | TWD2 Education and Research Network | Unclassified | IPv6 | 296 |
| AS151464 | Shanghai Luogu Network Technology Co., Ltd. | Unclassified | IPv4 IPv6 | 242 |
| AS209306 | Jin Shaohai | Unclassified | IPv4 IPv6 | 100 |
| AS57175 | Tianhai InfoTech Limited | Unclassified | IPv6 | 37 |
| AS135671 | RBB InfoTech | Unclassified | IPv6 | 37 |
| AS135674 | Kano Network | Unclassified | IPv6 | 21 |
Adjacency
Adjacent networks
Every AS seen directly next to AS4842 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 804 |
| AS24239 | TWD2 Education and Research Network | Unclassified | IPv6 | 317 |
| AS151464 | Shanghai Luogu Network Technology Co., Ltd. | Unclassified | IPv4 IPv6 | 242 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 157 |
| AS209306 | Jin Shaohai | Unclassified | IPv4 IPv6 | 100 |
| AS53356 | Free Range Cloud Hosting Inc. | Hosting | IPv4 IPv6 | 89 |
| AS57175 | Tianhai InfoTech Limited | Unclassified | IPv6 | 37 |
| AS135671 | RBB InfoTech | Unclassified | IPv6 | 37 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 23 |
| AS135674 | Kano Network | Unclassified | IPv6 | 21 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.