asn.dev

Observed topology

AS139597 WBP-AS-AP Wellcamp Business Park Pty Ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS139597: 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
AS4826Vocus Connect International BackboneUnclassifiedIPv445
AS6939Hurricane Electric LLCTransitIPv48
AS9268Over The Wire Pty LtdHostingIPv44
AS24482SG.GSHostingIPv41
AS64073Vetta GroupUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132859TheDC Pty LtdUnclassifiedIPv4118

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4826Vocus Connect International BackboneUnclassifiedIPv4135
AS132859TheDC Pty LtdUnclassifiedIPv4118
AS6939Hurricane Electric LLCTransitIPv424
AS9268Over The Wire Pty LtdHostingIPv412
AS24482SG.GSHostingIPv43
AS64073Vetta GroupUnclassifiedIPv43

Provenance

Where this comes from

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