asn.dev

Observed topology

AS152644 QINIU-AS-AP QINIU CHINA limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152644: 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 IPv6175
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6127
AS135338STARCLOUD INFORMATION LIMITEDUnclassifiedIPv470
AS154324AltusCloud Pte. Ltd.HostingIPv459
AS7552Viettel GroupMobileIPv422

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS154438Superstify Technology Pte LtdUnclassifiedIPv4176
AS154324AltusCloud Pte. Ltd.HostingIPv45

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6225
AS154438Superstify Technology Pte LtdUnclassifiedIPv4176
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6166
AS135338STARCLOUD INFORMATION LIMITEDUnclassifiedIPv496
AS7552Viettel GroupMobileIPv488
AS154324AltusCloud Pte. Ltd.HostingIPv464

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.