asn.dev

Observed topology

AS132789 PIVOTEL-AS-AP Pivotel Group Pty Limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS132789: 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
AS9507NextHop Pty LtdUnclassifiedIPv4 IPv6733
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6648
AS38195SuperloopUnclassifiedIPv4160
AS6939Hurricane Electric LLCTransitIPv440
AS1221Telstra LimitedMobileIPv414
AS24482SG.GSHostingIPv45
AS64073Vetta GroupUnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136973Pivotel Group Pty LimitedUnclassifiedIPv4240
AS136161Pivotel Group Pty LimitedUnclassifiedIPv497
AS41458Pulsar Solutions Inc.UnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9507NextHop Pty LtdUnclassifiedIPv4 IPv6843
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6648
AS38195SuperloopUnclassifiedIPv4389
AS136973Pivotel Group Pty LimitedUnclassifiedIPv4240
AS136161Pivotel Group Pty LimitedUnclassifiedIPv497
AS6939Hurricane Electric LLCTransitIPv440
AS1221Telstra LimitedMobileIPv414
AS24482SG.GSHostingIPv45
AS64073Vetta GroupUnclassifiedIPv45
AS41458Pulsar Solutions Inc.UnclassifiedIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 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.