Atlantis Telekomünikasyon bil. hizm. san.tic.ltd.şti.: 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. DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31

   Problem	PeeringDB has	The export has
   Port speed differs	400G	800G

   • In the entry with IPv4 80.81.196.172: set Speed to 800000 (800G) (now 400000).
2. DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:3f:0:3:1ea9:0:1
   Port speed differs	20G	100G

   • In the entry with IPv4 185.1.48.15: set IPv6 to 2001:7f8:3f:0:3:1ea9:0:1 (now empty); set Speed to 100000 (100G) (now 20000).
3. GNM-IX Amsterdam, Netherlands · PeeringDB 358

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2a03:5f80:4:2::237:14

   • In the entry with IPv4 178.18.237.14: set IPv6 to 2a03:5f80:4:2::237:14 (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.