Acquire BPO: PeeringDB fix list

Correct these entries (7)

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. GetaFIX Manila Manila, Philippines · PeeringDB 2345

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2401:fdc0::5:8907:1

   • In the entry with IPv4 103.104.19.121: set IPv6 to 2401:fdc0::5:8907: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. IX Australia Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7fa:11:1:0:e61b:0:1

   • In the entry with IPv4 218.100.78.145: set IPv6 to 2001:7fa:11:1:0:e61b:0: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.

3. IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:7fa:11:4:0:e61b:0:1

   • In the entry with IPv4 218.100.53.77: set IPv6 to 2001:7fa:11:4:0:e61b:0: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.

4. MegaIX Melbourne Melbourne, Australia · PeeringDB 779

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:dea:0:30::78

   • In the entry with IPv4 103.26.71.120: set IPv6 to 2001:dea:0:30::78 (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.

5. MegaIX Singapore Singapore, Singapore · PeeringDB 965

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:ded::2f

   • In the entry with IPv4 103.41.12.47: set IPv6 to 2001:ded::2f (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. MegaIX Sydney Sydney, Australia · PeeringDB 780

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

   • In the entry with IPv4 103.26.68.170: set IPv6 to 2001:dea:0:10::aa (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.

7. SGIX Singapore, Singapore · PeeringDB 429

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:de8:12:100::197

   • In the entry with IPv4 103.16.102.197: set IPv6 to 2001:de8:12:100::197 (now empty).