Swaziland PTC: PeeringDB fix list

Correct these entries (8)

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
   IPv6 address missing from PeeringDB	none	2001:7f8:1::a501:9711:1

   • In the entry with IPv4 80.249.212.89: set IPv6 to 2001:7f8:1::a501:9711: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.

2. DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8::4cff:0:2

   • In the entry with IPv4 80.81.196.36: set IPv6 to 2001:7f8::4cff:0:2 (now empty).
3. DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:d5::4cff:0:1
   Port speed differs	100M	10G

   • In the entry with IPv4 185.1.131.17: set IPv6 to 2001:7f8:d5::4cff:0:1 (now empty); set Speed to 10000 (10G) (now 100).
4. 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::4cff:0:1

   • In the entry with IPv4 206.82.104.253: set IPv6 to 2001:504:36::4cff:0:1 (now empty).
5. JINX Johannesburg, South Africa · PeeringDB 129

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:43f8:1f0::104

   • In the entry with IPv4 196.60.96.104: set IPv6 to 2001:43f8:1f0::104 (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.

6. LINX LON1 London, United Kingdom · PeeringDB 18

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:4::4cff:1
   Port speed differs	1G	2G

   • In the entry with IPv4 195.66.225.76: set IPv6 to 2001:7f8:4::4cff:1 (now empty); set Speed to 2000 (2G) (now 1000).
7. NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:43f8:6d1::245

   • In the entry with IPv4 196.60.70.245: set IPv6 to 2001:43f8:6d1::245 (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.

8. NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:43f8:6d0::30

   • In the entry with IPv4 196.60.8.30: set IPv6 to 2001:43f8:6d0::30 (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.