Fastrack Technology: 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. IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716

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

   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. LINX LON1 London, United Kingdom · PeeringDB 18

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

   • In the entry with IPv4 195.66.226.202: set IPv6 to 2001:7f8:4::e4d4:1 (now empty).
3. MegaIX Ashburn Ashburn, United States · PeeringDB 1178

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2606:a980:0:3::30

   • In the entry with IPv4 206.53.170.48: set IPv6 to 2606:a980:0:3::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.

4. MegaIX Melbourne Melbourne, Australia · PeeringDB 779

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

   • In the entry with IPv4 103.26.71.135: set IPv6 to 2001:dea:0:30::87 (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 Seattle Seattle, United States · PeeringDB 1174

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2606:a980:0:4::12

   • In the entry with IPv4 206.53.171.18: set IPv6 to 2606:a980:0:4::12 (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 Singapore Singapore, Singapore · PeeringDB 965

   Problem	PeeringDB has	The export has
   IPv6 address missing from PeeringDB	none	2001:ded::1b

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

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

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