asn.dev

Observed topology

AS141167 AGOTOZHKLIMITED-AS-AP - AgotoZ HK Limited

Unclassified APNIC

Upstreams 8 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 1
Upstream graph Who carries AS141167, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS141167 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS136897Enjoyvc Cloud Group Limited.HostingIPv4 IPv6702
AS4766Korea TelecomMobileIPv4413
AS174Cogent Communications, LLCTransitIPv4309
AS139076EnjoyVC Japan CorporationUnclassifiedIPv4220
AS41095IPTP LTDHostingIPv4213
AS137983TIANFENG (HONG KONG) COMMUNICATIONS LIMITEDUnclassifiedIPv4134
AS9957KINXHostingIPv49
AS138195MOACK.Co.LTDUnclassifiedIPv46

Transit

Downstream networks

inferred

Networks for which AS141167 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS9465AGOTOZ PTE. LTD.UnclassifiedIPv459

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS141167 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS136897Enjoyvc Cloud Group Limited.HostingIPv4 IPv6764
AS4766Korea TelecomMobileIPv4413
AS174Cogent Communications, LLCTransitIPv4309
AS139076EnjoyVC Japan CorporationUnclassifiedIPv4220
AS41095IPTP LTDHostingIPv4213
AS137983TIANFENG (HONG KONG) COMMUNICATIONS LIMITEDUnclassifiedIPv4134
AS9465AGOTOZ PTE. LTD.UnclassifiedIPv459
AS9957KINXHostingIPv49
AS138195MOACK.Co.LTDUnclassifiedIPv46
AS2914NTT America, Inc.TransitIPv43

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.