Actus: 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. AMS-IX Amsterdam, Netherlands · PeeringDB 26

   Problem	PeeringDB has	The export has
   Port speed differs	10G	500M

   • In the entry with IPv4 80.249.213.63: set Speed to 500 (500M) (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. DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31

   Problem	PeeringDB has	The export has
   IPv6 address differs	2001:7f8::3:49e:0:1	2001:7f8::3:49:0:1
   Port speed differs	10G	800G

   • In the entry with IPv4 80.81.192.150: set IPv6 to 2001:7f8::3:49:0:1 (now 2001:7f8::3:49e:0:1); set Speed to 800000 (800G) (now 10000).
3. LINX LON1 London, United Kingdom · PeeringDB 18

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

   • In the entry with IPv4 195.66.231.112: set IPv6 to 2001:7f8:4::3:49e:1 (now empty); set Speed to 1000 (1G) (now 10000).
4. THINX Warsaw Warsaw, Poland · PeeringDB 481

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	212.91.0.245	212.91.0.239 212.91.0.245
   IPv6 address missing from PeeringDB	2001:7f8:60::13:18	2001:7f8:60::13:17 2001:7f8:60::13:18
   Port speed differs	10G	2G

   • In the entry with IPv4 212.91.0.245: set IPv4 to (empty) (now 212.91.0.245); set Speed to 2000 (2G) (now 10000).
   • Add an entry: IPv4 –, IPv6 2001:7f8:60::13:17, speed 2000 (2G).
   • Add an entry: IPv4 212.91.0.239, IPv6 –, speed 2000 (2G).
   • Add an entry: IPv4 212.91.0.245, IPv6 –, speed 2000 (2G).

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