asn.dev

Observed topology

AS138571 SUPERCLOUDSLIMITED-AS-AP SUPERCLOUDS LIMITED

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS138571: 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
AS21859Zenlayer IncHostingIPv4 IPv6745
AS13444TRSUnclassifiedIPv4122
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4 IPv646
AS24482SG.GSHostingIPv4 IPv64
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS394881EK HOSTING INCUnclassifiedIPv4179

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS21859Zenlayer IncHostingIPv4 IPv6825
AS394881EK HOSTING INCUnclassifiedIPv4199
AS13444TRSUnclassifiedIPv4122
AS174Cogent Communications, LLCTransitIPv4119
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4 IPv646
AS24482SG.GSHostingIPv4 IPv64
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv43

Provenance

Where this comes from

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