Observed topology

AS131476 FUSIONBB-AU 1050 Market St

Unclassified APNIC

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS131476: 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
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	488
AS136557	Host Universal Pty Ltd	Unclassified	IPv4	120
AS6939	Hurricane Electric LLC	Transit	IPv4	80
AS24115	Equinix	Hosting	IPv4	10
AS24482	SG.GS	Hosting	IPv4	10
AS64073	Vetta Group	Unclassified	IPv4	10
AS18345	Servers Australia Customers	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS151603	D-Link Australia Pty Ltd	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	547
AS136557	Host Universal Pty Ltd	Unclassified	IPv4	120
AS6939	Hurricane Electric LLC	Transit	IPv4	80
AS151603	D-Link Australia Pty Ltd	Unclassified	IPv4	59
AS24115	Equinix	Hosting	IPv4	10
AS24482	SG.GS	Hosting	IPv4	10
AS64073	Vetta Group	Unclassified	IPv4	10
AS18345	Servers Australia Customers	Unclassified	IPv4	2

Provenance

Where this comes from

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