Observed topology

AS23686 ASN-EQIX-MELBOURNE-AP Equinix Asia Pacific

Unclassified ARIN

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23686: 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 IPv6	211

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS24015	SPI Networks, Electricity Distribution, Victoria	Unclassified	IPv4	295
AS24008	Hansen Technologies Doncaster	Unclassified	IPv4	159
AS24033	Australian Private Networks Pty Ltd	Unclassified	IPv4	59
AS203439	Dassault Systemes B.V.	Unclassified	IPv4	59
AS17987	.au Domain Administration	Unclassified	IPv4 IPv6	23
AS139006	Zoho Corporation PTY LTD	Unclassified	IPv4 IPv6	11

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4 IPv6	817
AS24015	SPI Networks, Electricity Distribution, Victoria	Unclassified	IPv4	295
AS24008	Hansen Technologies Doncaster	Unclassified	IPv4	159
AS24033	Australian Private Networks Pty Ltd	Unclassified	IPv4	59
AS203439	Dassault Systemes B.V.	Unclassified	IPv4	59
AS17987	.au Domain Administration	Unclassified	IPv4 IPv6	23
AS139006	Zoho Corporation PTY LTD	Unclassified	IPv4 IPv6	11

Provenance

Where this comes from

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