ICONIC SERVERS: PeeringDB fix list

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. LINX LON1 London, United Kingdom · PeeringDB 18

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:4::3:44ff:1
   Port speed differs	10G	100G

   • In the entry with IPv4 195.66.227.183: set IPv6 to 2001:7f8:4::3:44ff:1 (now empty); set Speed to 100000 (100G) (now 10000).
2. LONAP London, United Kingdom · PeeringDB 53

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:17::3:44ff:1

   • In the entry with IPv4 5.57.82.206: set IPv6 to 2001:7f8:17::3:44ff:1 (now empty).

   PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

3. 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::a521:4271:1 2001:7f8:13::a521:4271:2

   • In the entry with IPv4 193.239.116.11: set IPv6 to 2001:7f8:13::a521:4271:2 (now empty).
   • In the entry with IPv4 193.239.116.43: set IPv6 to 2001:7f8:13::a521:4271:1 (now empty).

   PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.