Observed topology

AS58907 AAPPL-AS-AP Acquire BPO Pty Ltd

Unclassified APNIC

Upstreams 11 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 11

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS58907: 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
AS6939	Hurricane Electric LLC	Transit	IPv4	150
AS134090	Leaptel	Residential	IPv4	137
AS9299	Philippine Long Distance Telephone Company	Unclassified	IPv4	46
AS174	Cogent Communications, LLC	Transit	IPv4	17
AS4775	Globe Telecoms	Unclassified	IPv4	13
AS24482	SG.GS	Hosting	IPv4	5
AS64073	Vetta Group	Unclassified	IPv4	4
AS293	ESnet	Unclassified	IPv4	2
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	1
AS37989	DCS1 Pte. Ltd.	Hosting	IPv4	1

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS58907 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

All 11

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	150
AS134090	Leaptel	Residential	IPv4	137
AS9299	Philippine Long Distance Telephone Company	Unclassified	IPv4	46
AS174	Cogent Communications, LLC	Transit	IPv4	17
AS4775	Globe Telecoms	Unclassified	IPv4	13
AS24482	SG.GS	Hosting	IPv4	5
AS64073	Vetta Group	Unclassified	IPv4	4
AS293	ESnet	Unclassified	IPv4	2
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	1
AS37989	DCS1 Pte. Ltd.	Hosting	IPv4	1

All 11 adjacent →

Provenance

Where this comes from

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