ixreport

Mistral-Compute: PeeringDB fix list

AS209952 · peeringdb.com/net/42085

PeeringDB

One thing to fix in Mistral-Compute's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Mistral-Compute'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 differs185.1.14.83185.1.14.121
    IPv6 address differs2001:7f8:12e::20:9952:12001:7f8:12e::20:9952:3
    Port speed differs400G1.2T
    • In the entry with IPv4 185.1.14.83: set IPv4 to 185.1.14.121 (now 185.1.14.83); set IPv6 to 2001:7f8:12e::20:9952:3 (now 2001:7f8:12e::20:9952:1); set Speed to 1200000 (1.2T) (now 400000).

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