Observed topology

AS132839 POWERLINE-AS-AP POWER LINE DATACENTER

Unclassified DROP-listed space APNIC

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

Upstream graph Who carries AS132839, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS132839 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS132839: 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.

AS	Network	Type	Families	Paths seen
AS13335	Cloudflare, Inc.	Hosting	IPv4	6,023
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	5,162
AS17476	CloudRadium (HK) Limited	Residential	IPv4	4,498
AS58453	China Mobile International Limited	Unclassified	IPv4	859
AS9304	HGC Global Communications Limited	Hosting	IPv4	318
AS23764	CTGNet	Unclassified	IPv4	10

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS13335	Cloudflare, Inc.	Hosting	IPv4	6,023
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	5,162
AS17476	CloudRadium (HK) Limited	Residential	IPv4	4,498
AS58453	China Mobile International Limited	Unclassified	IPv4	859
AS9304	HGC Global Communications Limited	Hosting	IPv4	318
AS23764	CTGNet	Unclassified	IPv4	10

Provenance

Where this comes from

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