ixreport

Enix: PeeringDB fix list

AS48813 · peeringdb.com/net/17012

PeeringDB

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

Make the changes on Enix'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. France nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France · PeeringDB 4705
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.14.45 185.1.14.46185.1.14.45
    IPv6 address in PeeringDB, not in the export2001:7f8:12e::4:8813:1 2001:7f8:12e::4:8813:22001:7f8:12e::4:8813:1
    Port speed differs2 × 100G100G
    • The entry with IPv4 185.1.14.46, IPv6 2001:7f8:12e::4:8813:2 isn't in the export: delete it if that connection is gone.

    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/48813/: 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.