ixreport

NetVault

AS56294 · VMvault Pty Ltd

11Exchanges
1On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
11Using the route servers
5To fix in PeeringDB
14Facilities in PeeringDB

Tools: Where can I peer with NetVault? · Where should NetVault peer next? · Compare NetVault with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

5 things to fix in NetVault's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on NetVault's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in NetVault's PeeringDB record. Add one entry per connection with these values.

  1. Australia IX Australia Perth (WA-IX) Perth, Australia · PeeringDB 21From its IX-F export

    2 connections, so 2 entries:

    IPv427.106.192.108
    IPv62001:7fa:11::db96:0:1
    Speed10000 Mbps (10G)
    RS peerYes
    IPv427.106.192.109
    IPv62001:7fa:11::db96:0:2
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Correct these entries (3)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:2:0:db96:0:1 2001:7fa:11:2:0:db96:0:2
    • In the entry with IPv4 218.100.76.56: set IPv6 to 2001:7fa:11:2:0:db96:0:1 (now empty).
    • In the entry with IPv4 218.100.76.58: set IPv6 to 2001:7fa:11:2:0:db96:0:2 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:1:0:db96:0:1 2001:7fa:11:1:0:db96:0:2
    • In the entry with IPv4 218.100.78.63: set IPv6 to 2001:7fa:11:1:0:db96:0:1 (now empty).
    • In the entry with IPv4 218.100.78.64: set IPv6 to 2001:7fa:11:1:0:db96:0:2 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:4:0:dbe6:0:1 2001:7fa:11:4:0:dbe6:0:2
    Port speed differs2 × 10G10G
    • In the entry with IPv4 218.100.52.123: set IPv6 to 2001:7fa:11:4:0:dbe6:0:2 (now empty).
    • In the entry with IPv4 218.100.52.131: set IPv6 to 2001:7fa:11:4:0:dbe6:0:1 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If NetVault has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30Not on its website members list
    IPv4210.171.225.150
    IPv6–
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

Exchanges over time

051015Oct 3, 2026Nov 19, 202611
Show as a table
DateExchanges
Nov 19, 202611
Nov 18, 202611
Nov 17, 202611
Nov 16, 202611
Nov 15, 202611
Nov 14, 202611
Nov 13, 202611
Nov 12, 202611
Nov 11, 202611
Nov 10, 202611
Nov 9, 202611
Nov 8, 202611
Nov 7, 202611
Nov 6, 202611
Nov 5, 202611
Nov 4, 202611
Nov 3, 202611
Nov 2, 202611
Nov 1, 202611
Oct 31, 202611
Oct 30, 202611
Oct 29, 202611
Oct 28, 202611
Oct 27, 202611
Oct 26, 202611
Oct 25, 202611
Oct 24, 202611
Oct 23, 202611
Oct 22, 202611
Oct 21, 202611
Oct 20, 202611
Oct 19, 202611
Oct 18, 202611
Oct 17, 202611
Oct 16, 202611
Oct 15, 202611
Oct 14, 202611
Oct 13, 202611
Oct 12, 202611
Oct 11, 202611
Oct 10, 202611
Oct 9, 202611
Oct 8, 202611
Oct 7, 202611
Oct 6, 202611
Oct 5, 202611
Oct 4, 202611
Oct 3, 202611

Map

Where NetVault's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 110G, at the 8 of 11 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Australia EdgeIX - Brisbane Brisbane, Australia 103.136.103.24 2001:df0:680:4::18 10G Yes PeeringDB
Australia EdgeIX - Perth Perth, Australia 103.136.102.72 2001:df0:680:3::48 10G Yes PeeringDB
Australia EdgeIX - Sydney Sydney, Australia 202.77.88.105 2001:df0:680:5::68 10G Yes Both
Australia IX Australia Brisbane (QLD-IX) Brisbane, Australia 218.100.76.56
218.100.76.58
2 × 10G Yes Both IPv6 not in PeeringDB
Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia 218.100.78.63
218.100.78.64
2 × 10G Yes Both IPv6 not in PeeringDB
Australia IX Australia Perth (WA-IX) Perth, Australia 27.106.192.108
27.106.192.109
2001:7fa:11::db96:0:1
2001:7fa:11::db96:0:2
10G Yes Not in PeeringDB
Australia IX Australia Sydney (NSW-IX) Sydney, Australia 218.100.52.123
218.100.52.131
2 × 10G Yes Both IPv6 not in PeeringDBSpeed differs
Japan JPIX TOKYO Tokyo, Japan 210.171.225.150 10G Yes PeeringDB only
Australia MegaIX Brisbane Brisbane, Australia 103.26.70.122 2001:dea:0:20::7a Yes Both
Australia MegaIX Melbourne Melbourne, Australia 103.26.71.117 2001:dea:0:30::75 Yes Both
Australia MegaIX Sydney Sydney, Australia 103.26.68.159 2001:dea:0:10::9f Yes Both

Exchanges in its buildings that it isn't on (14)

These exchanges have a switch in a facility where NetVault lists itself in PeeringDB, but don't have NetVault as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Japan BBIX TokyoTokyo, Japan 454 Digital Realty Tokyo - NRT10
Japan JPNAP TokyoTokyo, Japan 250 Digital Realty Tokyo - NRT10
Australia Equinix SydneySydney, Australia 219 Equinix SY3 - Sydney
Bulgaria NetIXSofia, Bulgaria 204 Equinix SY3 - Sydney
New Zealand AKL-IX (Auckland NZ)Auckland, New Zealand 106 Datacom - Orbit Data Centre (Auckland)
New Zealand MegaIX AucklandAuckland, New Zealand 93 Datacom - Orbit Data Centre (Auckland)
Australia EdgeIX - MelbourneMelbourne, Australia 73 NEXTDC M1; NEXTDC M2
Australia MegaIX PerthPerth, Australia 65 NEXTDC P1; NEXTDC P2
Australia IX Australia Adelaide (SA-IX)Adelaide, Australia 39 NEXTDC A1
Australia EdgeIX - AdelaideAdelaide, Australia 36 NEXTDC A1
New Zealand APEAuckland, New Zealand 28 Datacom - Orbit Data Centre (Auckland)
Australia MegaIX AdelaideAdelaide, Australia 24 NEXTDC A1
Australia EdgeIX - DarwinDarwin, Australia 9 NEXTDC D1
Australia ixFabricGlobal, Australia 2 Equinix SY3 - Sydney
Facilities (14)

The buildings NetVault lists in PeeringDB, and how many of the exchanges in each it's on.

Australia Equinix SY3 - SydneySydney 3 of 6
New Zealand Datacom - Orbit Data Centre (Auckland)Auckland 0 of 3
Japan Digital Realty Tokyo - NRT10Inzai-City 1 of 3
Australia NEXTDC A1Adelaide 0 of 3
Australia NEXTDC B1Brisbane 3 of 3
Australia NEXTDC B2Fortitude Valley 3 of 3
Australia NEXTDC M1Melbourne 2 of 3
Australia NEXTDC P1Málaga 2 of 3
Australia NEXTDC P2Perth 2 of 3
Australia NEXTDC S1Sydney 3 of 3
Australia NEXTDC S2Macquarie Park 3 of 3
Australia NEXTDC M2Tullamarine 1 of 2
Australia Equinix BR1 - Brisbane (formerly Metronode Brisbane 1)Brisbane 1 of 1
Australia NEXTDC D1Darwin 0 of 1