ixreport

FR-NIC-DNS-ANYCAST (AFNIC > NIC-FR > Anycast DNS): PeeringDB fix list

AS2484 · peeringdb.com/net/2858

PeeringDB

3 things to fix in FR-NIC-DNS-ANYCAST (AFNIC > NIC-FR > Anycast DNS)'s PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on FR-NIC-DNS-ANYCAST (AFNIC > NIC-FR > Anycast DNS)'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 (3)

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 AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 80.249.208.242: set Speed to 10000 (10G) (now 1000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs200M1G
    • In the entry with IPv4 80.81.194.155: set Speed to 1000 (1G) (now 200).
  3. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs10G1.25G
    • In the entry with IPv4 185.0.21.22: set Speed to 1250 (1.25G) (now 10000).

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