Opticomm Pty Ltd: 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. IX Australia Brisbane (QLD-IX) Brisbane, Australia · PeeringDB 576

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	218.100.76.119	218.100.76.23 218.100.76.119
   IPv6 address missing from PeeringDB	none	2001:7fa:11:2:0:b2c3:0:1
   Port speed differs	10G	2 × 10G

   • In the entry with IPv4 218.100.76.119: set IPv6 to 2001:7fa:11:2:0:b2c3:0:1 (now empty).
   • Add an entry: IPv4 218.100.76.23, IPv6 –, 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. IX Australia Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	218.100.78.48	218.100.78.22 218.100.78.48
   IPv6 address missing from PeeringDB	none	2001:7fa:11:1:0:b2c3:0:1 2001:7fa:11:1:2:bb3:0:2
   Port speed differs	100G	100G + 10G

   • In the entry with IPv4 218.100.78.48: set IPv6 to 2001:7fa:11:1:2:bb3:0:2 (now empty).
   • Add an entry: IPv4 218.100.78.22, IPv6 2001:7fa:11:1:0:b2c3:0:1, 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.

3. IX Australia Perth (WA-IX) Perth, Australia · PeeringDB 21

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

   • In the entry with IPv4 27.106.192.96: set IPv6 to 2001:7fa:11::b2c3:0:2 (now empty).

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

4. 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:b2c3:0:2

   • In the entry with IPv4 218.100.53.82: set IPv6 to 2001:7fa:11:4:0:b2c3:0:2 (now empty).

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

5. MegaIX Brisbane Brisbane, Australia · PeeringDB 781

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	103.26.70.106	103.26.70.57 103.26.70.106
   IPv6 address missing from PeeringDB	none	2001:dea:0:20::39 2001:dea:0:20::6a

   • In the entry with IPv4 103.26.70.106: set IPv6 to 2001:dea:0:20::6a (now empty).
   • Add an entry: IPv4 103.26.70.57, IPv6 2001:dea:0:20::39, RS peer no.

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

6. MegaIX Melbourne Melbourne, Australia · PeeringDB 779

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	103.26.71.152	103.26.71.149 103.26.71.152
   IPv6 address missing from PeeringDB	2001:dea:0:30::98	2001:dea:0:30::95 2001:dea:0:30::98

   • Add an entry: IPv4 103.26.71.149, IPv6 2001:dea:0:30::95, RS peer no.

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

7. MegaIX Perth Perth, Australia · PeeringDB 1235

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	202.12.243.72	202.12.243.29 202.12.243.72
   IPv6 address missing from PeeringDB	none	2001:dea:0:50::1d 2001:dea:0:50::48

   • In the entry with IPv4 202.12.243.72: set IPv6 to 2001:dea:0:50::48 (now empty).
   • Add an entry: IPv4 202.12.243.29, IPv6 2001:dea:0:50::1d, RS peer no.

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

8. MegaIX Sydney Sydney, Australia · PeeringDB 780

   Problem	PeeringDB has	The export has
   IPv4 address missing from PeeringDB	103.26.69.46	103.26.68.21 103.26.69.46
   IPv6 address missing from PeeringDB	2001:dea:0:10::12e	2001:dea:0:10::15 2001:dea:0:10::12e

   • Add an entry: IPv4 103.26.68.21, IPv6 2001:dea:0:10::15, RS peer no.

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