NetVault
AS56294 · VMvault Pty Ltd
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.
-
2 connections, so 2 entries:
IPv4 27.106.192.108 IPv6 2001:7fa:11::db96:0:1 Speed 10000 Mbps (10G) RS peer Yes IPv4 27.106.192.109 IPv6 2001:7fa:11::db96:0:2 Speed 10000 Mbps (10G) RS peer Yes 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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:11:4:0:dbe6:0:1 2001:7fa:11:4:0:dbe6:0:2 Port speed differs 2 × 10G 10G - 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.
-
IPv4 210.171.225.150 IPv6 – Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 11 |
| Nov 18, 2026 | 11 |
| Nov 17, 2026 | 11 |
| Nov 16, 2026 | 11 |
| Nov 15, 2026 | 11 |
| Nov 14, 2026 | 11 |
| Nov 13, 2026 | 11 |
| Nov 12, 2026 | 11 |
| Nov 11, 2026 | 11 |
| Nov 10, 2026 | 11 |
| Nov 9, 2026 | 11 |
| Nov 8, 2026 | 11 |
| Nov 7, 2026 | 11 |
| Nov 6, 2026 | 11 |
| Nov 5, 2026 | 11 |
| Nov 4, 2026 | 11 |
| Nov 3, 2026 | 11 |
| Nov 2, 2026 | 11 |
| Nov 1, 2026 | 11 |
| Oct 31, 2026 | 11 |
| Oct 30, 2026 | 11 |
| Oct 29, 2026 | 11 |
| Oct 28, 2026 | 11 |
| Oct 27, 2026 | 11 |
| Oct 26, 2026 | 11 |
| Oct 25, 2026 | 11 |
| Oct 24, 2026 | 11 |
| Oct 23, 2026 | 11 |
| Oct 22, 2026 | 11 |
| Oct 21, 2026 | 11 |
| Oct 20, 2026 | 11 |
| Oct 19, 2026 | 11 |
| Oct 18, 2026 | 11 |
| Oct 17, 2026 | 11 |
| Oct 16, 2026 | 11 |
| Oct 15, 2026 | 11 |
| Oct 14, 2026 | 11 |
| Oct 13, 2026 | 11 |
| Oct 12, 2026 | 11 |
| Oct 11, 2026 | 11 |
| Oct 10, 2026 | 11 |
| Oct 9, 2026 | 11 |
| Oct 8, 2026 | 11 |
| Oct 7, 2026 | 11 |
| Oct 6, 2026 | 11 |
| Oct 5, 2026 | 11 |
| Oct 4, 2026 | 11 |
| Oct 3, 2026 | 11 |
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.
| EdgeIX - Brisbane Brisbane, Australia | 10G | PeeringDB | |
| EdgeIX - Perth Perth, Australia | 10G | PeeringDB | |
| EdgeIX - Sydney Sydney, Australia | 10G | Both | |
| IX Australia Brisbane (QLD-IX) Brisbane, Australia | 2 × 10G | Both IPv6 not in PeeringDB | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 2 × 10G | Both IPv6 not in PeeringDB | |
| IX Australia Perth (WA-IX) Perth, Australia | 10G | Not in PeeringDB | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 2 × 10G | Both IPv6 not in PeeringDBSpeed differs | |
| JPIX TOKYO Tokyo, Japan | 10G | PeeringDB only | |
| MegaIX Brisbane Brisbane, Australia | Both | ||
| MegaIX Melbourne Melbourne, Australia | Both | ||
| MegaIX Sydney Sydney, Australia | Both |
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.
| BBIX TokyoTokyo, Japan | 454 | |
| JPNAP TokyoTokyo, Japan | 250 | |
| Equinix SydneySydney, Australia | 219 | |
| NetIXSofia, Bulgaria | 204 | |
| AKL-IX (Auckland NZ)Auckland, New Zealand | 106 | |
| MegaIX AucklandAuckland, New Zealand | 93 | |
| EdgeIX - MelbourneMelbourne, Australia | 73 | |
| MegaIX PerthPerth, Australia | 65 | |
| IX Australia Adelaide (SA-IX)Adelaide, Australia | 39 | |
| EdgeIX - AdelaideAdelaide, Australia | 36 | |
| APEAuckland, New Zealand | 28 | |
| MegaIX AdelaideAdelaide, Australia | 24 | |
| EdgeIX - DarwinDarwin, Australia | 9 | |
| ixFabricGlobal, Australia | 2 |
Facilities (14)
The buildings NetVault lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix SY3 - SydneySydney | 3 of 6 | |
| Datacom - Orbit Data Centre (Auckland)Auckland | 0 of 3 | |
| Digital Realty Tokyo - NRT10Inzai-City | 1 of 3 | |
| NEXTDC A1Adelaide | 0 of 3 | |
| NEXTDC B1Brisbane | 3 of 3 | |
| NEXTDC B2Fortitude Valley | 3 of 3 | |
| NEXTDC M1Melbourne | 2 of 3 | |
| NEXTDC P1Málaga | 2 of 3 | |
| NEXTDC P2Perth | 2 of 3 | |
| NEXTDC S1Sydney | 3 of 3 | |
| NEXTDC S2Macquarie Park | 3 of 3 | |
| NEXTDC M2Tullamarine | 1 of 2 | |
| Equinix BR1 - Brisbane (formerly Metronode Brisbane 1)Brisbane | 1 of 1 | |
| NEXTDC D1Darwin | 0 of 1 |