Observed topology
AS141167 AGOTOZHKLIMITED-AS-AP - AgotoZ HK Limited
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS141167: 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 |
|---|---|---|---|---|
| AS136897 | Enjoyvc Cloud Group Limited. | Hosting | IPv4 IPv6 | 702 |
| AS4766 | Korea Telecom | Mobile | IPv4 | 413 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 309 |
| AS139076 | EnjoyVC Japan Corporation | Unclassified | IPv4 | 220 |
| AS41095 | IPTP LTD | Hosting | IPv4 | 213 |
| AS137983 | TIANFENG (HONG KONG) COMMUNICATIONS LIMITED | Unclassified | IPv4 | 134 |
| AS9957 | KINX | Hosting | IPv4 | 9 |
| AS138195 | MOACK.Co.LTD | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS141167 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9465 | AGOTOZ PTE. LTD. | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS141167 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS136897 | Enjoyvc Cloud Group Limited. | Hosting | IPv4 IPv6 | 764 |
| AS4766 | Korea Telecom | Mobile | IPv4 | 413 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 309 |
| AS139076 | EnjoyVC Japan Corporation | Unclassified | IPv4 | 220 |
| AS41095 | IPTP LTD | Hosting | IPv4 | 213 |
| AS137983 | TIANFENG (HONG KONG) COMMUNICATIONS LIMITED | Unclassified | IPv4 | 134 |
| AS9465 | AGOTOZ PTE. LTD. | Unclassified | IPv4 | 59 |
| AS9957 | KINX | Hosting | IPv4 | 9 |
| AS138195 | MOACK.Co.LTD | Unclassified | IPv4 | 6 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 3 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-04 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.33M 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.