Interconnection

AS9507 NEXTHOP-AS-AP NextHop Pty Ltd

Unclassified APNIC

Exchanges 10 10 active

Countries 4 most in Australia

Regions 2

Largest fabric 496 Equinix Internet Exchange Singapore

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS9507, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's page, with its peering LANs and everyone else on it.

Asia-Pacific 8 North America 2

Exchange	Location	Their address	Policy	Member ports
Equinix Internet Exchange Singapore	Singapore, Singapore	27.111.228.190	Open	496
BroadBand Internet eXchange Tokyo	Tokyo, Japan	101.203.90.141	Open	361
Coresite - Any2 West	Los Angeles, United States	206.72.211.201	Open	344
Any2 California	Los Angeles, United States	206.72.211.201	Open	319
Equinix Internet Exchange Sydney	Sydney, Australia	45.127.172.147	Open	238
Edge Internet Exchange - Sydney	Sydney, Australia	202.77.88.5	Open	163
Edge Internet Exchange - Perth	Perth, Australia	103.136.102.20	Open	80
Edge Internet Exchange - Melbourne	Melbourne, Australia	202.77.90.38	Open	74
Equinix Internet Exchange Melbourne	Melbourne, Australia	183.177.61.79	Open	58
Edge Internet Exchange - Brisbane	Brisbane, Australia	103.136.103.3	—	56

Recorded rather than inferred: an address on a peering LAN is at that exchange by definition. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. An absent exchange means PCH has no record of it, not that the network is not there. For the operator's own claims, see its PeeringDB record.

From the exchange directory collected 2026-10-10 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,215 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.