asn.dev

Observed topology

AS131270 PTGL-AS-AP - Planet Technology Group Ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS131270: 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 IPv6214
AS38195SuperloopUnclassifiedIPv488
AS24482SG.GSHostingIPv4 IPv617
AS64073Vetta GroupUnclassifiedIPv4 IPv617
AS35280F5 Networks SARLHostingIPv4 IPv615
AS24115EquinixHostingIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS38835Buroserv Australia Pty LtdUnclassifiedIPv45,360

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38835Buroserv Australia Pty LtdUnclassifiedIPv45,360
AS4764Aussie BroadbandResidentialIPv42,846
AS6939Hurricane Electric LLCTransitIPv4 IPv61,990
AS38195SuperloopUnclassifiedIPv4249
AS24482SG.GSHostingIPv4 IPv6178
AS64073Vetta GroupUnclassifiedIPv4 IPv6178
AS24115EquinixHostingIPv4174
AS35280F5 Networks SARLHostingIPv4 IPv6110

Provenance

Where this comes from

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