asn.dev

Observed topology

AS10089 DTNCORP-TH-AP Total Access Communication PLC.

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10089: 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
AS38082True International Gateway Co., Ltd.UnclassifiedIPv4 IPv6213
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv655

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS139057Edgenext Legend Dynasty Pte. Ltd.UnclassifiedIPv4 IPv6120
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv696
AS7470TRUE INTERNET Co.,Ltd.ResidentialIPv460
AS396986Bytedance Inc.HostingIPv612
AS135419Cableconnect Co.,LtdHostingIPv4 IPv64

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38082True International Gateway Co., Ltd.UnclassifiedIPv4 IPv6445
AS139057Edgenext Legend Dynasty Pte. Ltd.UnclassifiedIPv4 IPv6120
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv6117
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv696
AS7470TRUE INTERNET Co.,Ltd.ResidentialIPv460
AS396986Bytedance Inc.HostingIPv612
AS135419Cableconnect Co.,LtdHostingIPv4 IPv66

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.