ixreport

Mercury NZ: PeeringDB fix list

AS55850 · peeringdb.com/net/7924

PeeringDB

2 things to fix in Mercury NZ's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Mercury NZ'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 (2)

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. New Zealand AKL-IX (Auckland NZ) Auckland, New Zealand · PeeringDB 977
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB43.243.21.6743.243.21.67 43.243.21.102
    IPv6 address missing from PeeringDB2001:7fa:11:6:0:da2a:0:12001:7fa:11:6:0:da2a:0:1 2001:7fa:11:6:0:da2a:0:2
    • Add an entry: IPv4 43.243.21.102, IPv6 2001:7fa:11:6:0:da2a:0:2, 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.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs5G400G
    • In the entry with IPv4 80.81.195.161: set Speed to 400000 (400G) (now 5000).

From ixreport.com/net/55850/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.