Enegan: PeeringDB fix list

AS208808 · peeringdb.com/net/25128

PeeringDB

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

Make the changes on Enegan'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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs400G800G
    • In the entry with IPv4 80.81.192.221: set Speed to 800000 (800G) (now 400000).
  2. Italy MIX Roma Rome, Italy · PeeringDB 4377
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:101:14::14
    • In the entry with IPv4 185.188.83.14: set IPv6 to 2001:7f8:101:14::14 (now empty).

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