Network Platforms: PeeringDB fix list

Correct these entries (5)

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. CINX Cape Town, South Africa · PeeringDB 344

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	196.223.22.86	196.223.22.86 196.223.23.112
   IPv6 address missing from PeeringDB	2001:43f8:1f1::86	2001:43f8:1f1::86 2001:43f8:1f1::1:112
   Port speed differs	10G	10G + 1G

   • In the entry with IPv4 196.223.22.86: set Speed to 1000 (1G) (now 10000).
   • Add an entry: IPv4 196.223.23.112, IPv6 2001:43f8:1f1::1:112, speed 10000 (10G), RS peer yes.

   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
   Port speed differs	1G	100G

   • In the entry with IPv4 80.81.193.38: set Speed to 100000 (100G) (now 1000).
3. JINX Johannesburg, South Africa · PeeringDB 129

   Problem	PeeringDB has	The export has
   Port speed differs	2 × 10G	10G + 1G

   • In the entry with IPv4 196.60.96.86: 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.

4. LINX LON1 London, United Kingdom · PeeringDB 18

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

   • In the entry with IPv4 195.66.224.25: set Speed to 8000 (8G) (now 10000).
5. NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592

   Problem	PeeringDB has	The export has
   Port speed differs	2 × 10G	20G + 2 × 10G

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