asn.dev

Observed topology

AS132849 BANDWIDTH-AS-AP - Bandwidth Holdings PTY LTD

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS132849: 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
AS136935LocalPref Pty LtdUnclassifiedIPv455
AS7575Australian Academic and Research Network (AARNet)EducationIPv42
AS9507NextHop Pty LtdUnclassifiedIPv42
AS24482SG.GSHostingIPv42
AS58505Kohen Technology Group Pty LtdResidentialIPv42
AS24516Virtutel Pty LtdUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS139603Xenex Systems PTY LTDHostingIPv4115
AS58505Kohen Technology Group Pty LtdResidentialIPv442

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS139603Xenex Systems PTY LTDHostingIPv4115
AS136935LocalPref Pty LtdUnclassifiedIPv4111
AS24516Virtutel Pty LtdUnclassifiedIPv4100
AS58505Kohen Technology Group Pty LtdResidentialIPv444
AS24482SG.GSHostingIPv44
AS7575Australian Academic and Research Network (AARNet)EducationIPv42
AS9507NextHop Pty LtdUnclassifiedIPv42

Provenance

Where this comes from

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