ixreport

Electrica: PeeringDB fix list

AS49821 · peeringdb.com/net/32122

PeeringDB

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

Make the changes on Electrica'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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.225.167178.18.225.117 178.18.225.148 178.18.225.167
    IPv6 address missing from PeeringDB2a03:5f80:4::225:1672a03:5f80:4::225:117 2a03:5f80:4::225:148 2a03:5f80:4::225:167
    Port speed differs50G100G + 70G
    • In the entry with IPv4 178.18.225.167: set Speed to 70000 (70G) (now 50000).
    • Add an entry: IPv4 178.18.225.117, IPv6 2a03:5f80:4::225:117, speed 100000 (100G), RS peer yes.
    • Add an entry: IPv4 178.18.225.148, IPv6 2a03:5f80:4::225:148, speed 100000 (100G), 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/49821/: 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.