PrimoWireless: PeeringDB fix list

AS132255 · peeringdb.com/net/7958

PeeringDB

2 things to fix in PrimoWireless's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on PrimoWireless'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 PrimoWireless's PeeringDB record. Add one entry per connection with these values.

  1. Australia EdgeIX - Sydney Sydney, Australia · PeeringDB 2761From its website members list
    IPv4202.77.88.99
    IPv62001:df0:680:5::98
    SpeedNot published
    RS peerNot published

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. New Zealand MegaIX Auckland Auckland, New Zealand · PeeringDB 984
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:40::31
    • In the entry with IPv4 43.243.22.49: set IPv6 to 2001:dea:0:40::31 (now empty).

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

From ixreport.com/net/132255/: 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.