asn.dev

Observed topology

AS38566 NTTCT-AS-TH-AP NTTCTNET

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38566: 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
AS2914NTT America, Inc.TransitIPv4 IPv6275
AS4651National Telecom Public Company LimitedUnclassifiedIPv4227
AS17645ASN - NTT SINGAPORE PTE LTDUnclassifiedIPv465
AS132876Symphony Communication (Thailand) PCL.HostingIPv4 IPv662
AS24482SG.GSHostingIPv4 IPv611

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17978SERVCORP AUSTRALIAN HOLDINGS LTDUnclassifiedIPv4195
AS17645ASN - NTT SINGAPORE PTE LTDUnclassifiedIPv44
AS24237Siam City Cement Public Company Limited (SCCC)UnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6275
AS132876Symphony Communication (Thailand) PCL.HostingIPv4 IPv6250
AS4651National Telecom Public Company LimitedUnclassifiedIPv4227
AS17978SERVCORP AUSTRALIAN HOLDINGS LTDUnclassifiedIPv4195
AS17645ASN - NTT SINGAPORE PTE LTDUnclassifiedIPv475
AS24482SG.GSHostingIPv4 IPv618
AS24237Siam City Cement Public Company Limited (SCCC)UnclassifiedIPv42

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.