NU Informationssysteme: PeeringDB fix list

Correct these entries (5)

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. BCIX Berlin, Germany · PeeringDB 87

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:19:1::c382:1
   Port speed differs	10G	2G

   • In the entry with IPv4 193.178.185.83: set IPv6 to 2001:7f8:19:1::c382:1 (now empty); set Speed to 2000 (2G) (now 10000).

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

2. MegaIX Berlin Berlin, Germany · PeeringDB 209

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:8:5:0:c382:0:1

   • In the entry with IPv4 194.9.117.3: set IPv6 to 2001:7f8:8:5:0:c382:0:1 (now empty).

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

3. MegaIX Dusseldorf Dusseldorf, Germany · PeeringDB 91

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:8::c382:0:1

   • In the entry with IPv4 194.146.118.9: set IPv6 to 2001:7f8:8::c382:0:1 (now empty).

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

4. MegaIX Frankfurt Frankfurt, Germany · PeeringDB 676

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:8:20:0:c382:0:1

   • In the entry with IPv4 62.69.146.7: set IPv6 to 2001:7f8:8:20:0:c382:0:1 (now empty).

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

5. NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:13::a505:50:1

   • In the entry with IPv4 193.239.116.174: set IPv6 to 2001:7f8:13::a505:50:1 (now empty).

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