asn.dev

Observed topology

AS58430 NDM-AS-AP TCC Technology Co., Ltd.

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58430: 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
AS38040TOT Public Company LimitedUnclassifiedIPv452
AS2914NTT America, Inc.TransitIPv49
AS17639Converge ICT Solutions Inc.UnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS38001NewMedia Express Pte LtdHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17887T.C.C. Technology Co., Ltd.ResidentialIPv4 IPv62,572
AS45223World Internetwork Co.,Ltd , Thailand.HostingIPv4311
AS55256Netskope IncHostingIPv4247
AS56038RackCorpHostingIPv4104
AS140918CMKL UniversityUnclassifiedIPv4 IPv699
AS152127OneAsia Data Center (BKK1) Company LimitedUnclassifiedIPv61

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS17887T.C.C. Technology Co., Ltd.ResidentialIPv4 IPv62,872
AS38040TOT Public Company LimitedUnclassifiedIPv4 IPv62,833
AS2914NTT America, Inc.TransitIPv4 IPv6663
AS45223World Internetwork Co.,Ltd , Thailand.HostingIPv4311
AS55256Netskope IncHostingIPv4247
AS6939Hurricane Electric LLCTransitIPv4 IPv6154
AS56038RackCorpHostingIPv4104
AS140918CMKL UniversityUnclassifiedIPv4 IPv699
AS38001NewMedia Express Pte LtdHostingIPv4 IPv633
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv612

All 14 adjacent →

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.