IT7 Networks: 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. DE-CIX New York New York, United States · PeeringDB 804

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:504:36::64dc:0:1

   • In the entry with IPv4 206.82.105.15: set IPv6 to 2001:504:36::64dc:0:1 (now empty).
2. ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:12a::138

   • In the entry with IPv4 185.1.240.138: set IPv6 to 2001:7f8:12a::138 (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. FogIXP Avers, Switzerland · PeeringDB 3756

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:ca:1:0:2:5820:1

   • In the entry with IPv4 185.1.147.140: set IPv6 to 2001:7f8:ca:1:0:2:5820: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.

4. 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::a502:5820:1

   • In the entry with IPv4 193.239.118.207: set IPv6 to 2001:7f8:13::a502:5820: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.

5. SFMIX San Francisco, United States · PeeringDB 155

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:504:30::ba02:5820:1

   • In the entry with IPv4 206.197.187.37: set IPv6 to 2001:504:30::ba02:5820:1 (now empty).