ixreport

VERNet

AS56123 · VERN

VERNet Pty Ltd

1Exchange
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in VERNet's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

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

Correct these entries (1)

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. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB103.26.71.72103.26.71.72 103.26.71.111
    IPv6 address missing from PeeringDB2001:dea:0:30::482001:dea:0:30::48 2001:dea:0:30::6f
    • Add an entry: IPv4 103.26.71.111, IPv6 2001:dea:0:30::6f, RS peer no.

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

Exchanges over time

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

Map

Where VERNet'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 1G across 1 exchange.

Australia MegaIX Melbourne Melbourne, Australia 103.26.71.72 2001:dea:0:30::48 1G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB

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

These exchanges have a switch in a facility where VERNet lists itself in PeeringDB, but don't have VERNet 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.

Australia IX Australia Melbourne (VIC-IX)Melbourne, Australia 106 NEXTDC M1
Australia EdgeIX - MelbourneMelbourne, Australia 73 NEXTDC M1
Australia Equinix MelbourneMelbourne, Australia 55 Equinix ME5 - Melbourne (formerly Metronode Melbourne 1)
Facilities (2)

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

Australia NEXTDC M1Melbourne 1 of 3
Australia Equinix ME5 - Melbourne (formerly Metronode Melbourne 1)Melbourne 1 of 2