asn.dev

Interconnection

AS56294 VMVAULT-AS-AP VMvault Pty Ltd

Residential APNIC Cable/DSL/ISP

Exchanges 11 11 active
Countries 2 most in Australia
Regions 1
Largest fabric 300 JPIX Tokyo

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS56294, 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 11

ExchangeLocationTheir addressPolicyMember ports
JPIX TokyoTokyo, Japan210.171.225.150Open300
Megaport IX SydneySydney, Australia103.26.68.159Open268
IX Australia (Sydney NSW)Sydney, Australia218.100.52.131Open195
Edge Internet Exchange - SydneySydney, Australia202.77.88.105Open163
Megaport IX MelbourneMelbourne, Australia103.26.71.117Open153
Megaport IX BrisbaneBrisbane, Australia103.26.70.122Open112
IX Australia (Melbourne VIC)Melbourne, Australia218.100.78.63—106
IX Australia (Perth WA)Perth, Australia27.106.192.109—81
Edge Internet Exchange - PerthPerth, Australia103.136.102.72Open80
IX Australia (Brisbane QLD)Brisbane, Australia218.100.76.56—77
Edge Internet Exchange - BrisbaneBrisbane, Australia103.136.103.24—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-26 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,347 exchanges and 97,624 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.