asn.dev

Observed topology

AS9664 SATPL-AS-AP SOUTHEAST ASIA TELECOMSG PTE. LTD.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9664: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6671
AS44356Epsilon Telecommunications LtdUnclassifiedIPv4137
AS24482SG.GSHostingIPv4 IPv622
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv622
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv65
AS38001NewMedia Express Pte LtdHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152179GLOBAL COMMUNICATION NETWORK LIMITEDResidentialIPv4236

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6707
AS44356Epsilon Telecommunications LtdUnclassifiedIPv4321
AS152179GLOBAL COMMUNICATION NETWORK LIMITEDResidentialIPv4236
AS24482SG.GSHostingIPv4 IPv626
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv626
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv69
AS38001NewMedia Express Pte LtdHostingIPv47

Provenance

Where this comes from

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