Observed topology

AS7600 ESCAPE-NET-AS - Escape.net

Residential APNIC

Upstreams 8 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7600: 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
AS174	Cogent Communications, LLC	Transit	IPv4	1,090
AS7474	SingTel Optus Pty Ltd	Unclassified	IPv4 IPv6	334
AS6939	Hurricane Electric LLC	Transit	IPv4	303
AS24482	SG.GS	Hosting	IPv4	31
AS4608	Asia Pacific Network Information Centre	Unclassified	IPv4	28
AS64073	Vetta Group	Unclassified	IPv4	23
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	3
AS35280	F5 Networks SARL	Hosting	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS56037	Escapenet Pty Ltd	Unclassified	IPv4	148

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	1,162
AS7474	SingTel Optus Pty Ltd	Unclassified	IPv4 IPv6	356
AS6939	Hurricane Electric LLC	Transit	IPv4	343
AS56037	Escapenet Pty Ltd	Unclassified	IPv4	148
AS24482	SG.GS	Hosting	IPv4	35
AS4608	Asia Pacific Network Information Centre	Unclassified	IPv4	32
AS64073	Vetta Group	Unclassified	IPv4	27
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	3
AS35280	F5 Networks SARL	Hosting	IPv4	3

Provenance

Where this comes from

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