ixreport

GLEIF: PeeringDB fix list

AS210752 · peeringdb.com/net/29977

PeeringDB

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

Make the changes on GLEIF'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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB80.81.196.121 is AS214565 EMPEIRIA AI LTD80.81.196.121
    IPv6 address missing from PeeringDB2001:7f8::3:3740:0:1 2001:7f8::3:3740:0:22001:7f8::3:3740:0:1 2001:7f8::3:3740:0:2 2001:7f8::3:3740:0:3
    Port speed differs2 × 1G800G + 2 × 1G

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • Add an entry: IPv4 –, IPv6 2001:7f8::3:3740:0:3, speed 800000 (800G), RS peer yes.

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