Borwood: 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. JINX Johannesburg, South Africa · PeeringDB 129

   Problem	PeeringDB has	The export has
   Port speed differs	10G	1G

   • In the entry with IPv4 196.60.96.190: set Speed to 1000 (1G) (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. KIXP - Nairobi Nairobi, Kenya · PeeringDB 236

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:43f8:60:1::127

   • In the entry with IPv4 196.223.21.127: set IPv6 to 2001:43f8:60:1::127 (now empty).
3. LINX LON1 London, United Kingdom · PeeringDB 18

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

   • In the entry with IPv4 195.66.226.80: set IPv6 to 2001:7f8:4::73a6:1 (now empty); set Speed to 4000 (4G) (now 10000).
4. LINX LON2 London, United Kingdom · PeeringDB 321

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7f8:4:1::73a6:1

   • In the entry with IPv4 195.66.238.80: set IPv6 to 2001:7f8:4:1::73a6:1 (now empty).
5. MegaIX Sydney Sydney, Australia · PeeringDB 780

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:dea:0:10::fc

   • In the entry with IPv4 103.26.68.252: set IPv6 to 2001:dea:0:10::fc (now empty).

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

6. 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::16

   • In the entry with IPv4 196.60.70.16: set IPv6 to 2001:43f8:6d1::16 (now empty).

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

7. NAPAfrica IX Durban Durban, South Africa · PeeringDB 969

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:43f8:6d2::119
   Port speed differs	1G	10G

   • In the entry with IPv4 196.10.141.119: set IPv6 to 2001:43f8:6d2::119 (now empty); set Speed to 10000 (10G) (now 1000).

   PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change 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::9606

   • In the entry with IPv4 196.60.8.11: set IPv6 to 2001:43f8:6d0::9606 (now empty).

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