Florian Voit: PeeringDB fix list

Correct these entries (4)

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. 3AM Network IX Amsterdam, Netherlands · PeeringDB 5023

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	none	91.213.211.93

   • In the entry with IPv6 2001:7f8:17d::93: set IPv4 to 91.213.211.93 (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.

2. INTERIX Amsterdam, Netherlands · PeeringDB 3990

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	none	185.1.185.19

   • In the entry with IPv6 2001:7f8:134::110: set IPv4 to 185.1.185.19 (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. Kawaii IX AMS Amsterdam, Netherlands · PeeringDB 4973

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	none	195.60.92.116

   • In the entry with IPv6 2602:f93b:1a35:1311::116: set IPv4 to 195.60.92.116 (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
   IPv4 address missing from PeeringDB	none	193.239.119.127

   • In the entry with IPv6 2001:7f8:13::a521:8218:1: set IPv4 to 193.239.119.127 (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.