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

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

   • In the entry with IPv4 196.223.22.24: set Speed to 10000 (10G) (now 1000).

   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. 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::34

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

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

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

   • In the entry with IPv4 196.60.8.227: set IPv6 to 2001:43f8:6d0::227 (now empty).
   • In the entry with IPv4 196.60.8.66: set IPv6 to 2001:43f8:6d0::66 (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.

4. NMBINX Gqeberha, South Africa · PeeringDB 4148

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:43f8:690::24

   • In the entry with IPv4 196.60.120.24: set IPv6 to 2001:43f8:690::24 (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.