ixreport

EP2 Payments: PeeringDB fix list

AS64044 · peeringdb.com/net/9006

PeeringDB

One thing to fix in EP2 Payments's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on EP2 Payments'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 Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB103.26.69.1103.26.69.1 103.26.69.36
    IPv6 address missing from PeeringDB2001:dea:0:10::1012001:dea:0:10::101 2001:dea:0:10::124
    • Add an entry: IPv4 103.26.69.36, IPv6 2001:dea:0:10::124, 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.

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