Opticomm Pty Ltd
AS45763
Tools: Where can I peer with Opticomm Pty Ltd? · Where should Opticomm Pty Ltd peer next? · Compare Opticomm Pty Ltd with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in Opticomm Pty Ltd's PeeringDB record, from what its exchanges publish: 8 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Opticomm Pty Ltd's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 13 |
| Nov 18, 2026 | 13 |
| Nov 17, 2026 | 13 |
| Nov 16, 2026 | 13 |
| Nov 15, 2026 | 13 |
| Nov 14, 2026 | 13 |
| Nov 13, 2026 | 13 |
| Nov 12, 2026 | 13 |
| Nov 11, 2026 | 13 |
| Nov 10, 2026 | 13 |
| Nov 9, 2026 | 13 |
| Nov 8, 2026 | 13 |
| Nov 7, 2026 | 13 |
| Nov 6, 2026 | 13 |
| Nov 5, 2026 | 13 |
| Nov 4, 2026 | 13 |
| Nov 3, 2026 | 13 |
| Nov 2, 2026 | 13 |
| Nov 1, 2026 | 13 |
| Oct 31, 2026 | 13 |
| Oct 30, 2026 | 13 |
| Oct 29, 2026 | 13 |
| Oct 28, 2026 | 13 |
| Oct 27, 2026 | 13 |
| Oct 26, 2026 | 13 |
| Oct 25, 2026 | 13 |
| Oct 24, 2026 | 13 |
| Oct 23, 2026 | 13 |
| Oct 22, 2026 | 13 |
| Oct 21, 2026 | 13 |
| Oct 20, 2026 | 13 |
| Oct 19, 2026 | 13 |
| Oct 18, 2026 | 13 |
| Oct 17, 2026 | 13 |
| Oct 16, 2026 | 13 |
| Oct 15, 2026 | 13 |
| Oct 14, 2026 | 13 |
| Oct 13, 2026 | 13 |
| Oct 12, 2026 | 13 |
| Oct 11, 2026 | 13 |
| Oct 10, 2026 | 13 |
| Oct 9, 2026 | 13 |
| Oct 8, 2026 | 13 |
| Oct 7, 2026 | 13 |
| Oct 6, 2026 | 13 |
| Oct 5, 2026 | 13 |
| Oct 4, 2026 | 13 |
| Oct 3, 2026 | 13 |
Map
Where Opticomm Pty Ltd's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| EdgeIX - Brisbane Brisbane, Australia | 10G | PeeringDB | |
| EdgeIX - Melbourne Melbourne, Australia | 10G | PeeringDB | |
| EdgeIX - Perth Perth, Australia | 10G | PeeringDB | |
| EdgeIX - Sydney Sydney, Australia | 100G | Both | |
| Equinix Sydney Sydney, Australia | 100G | PeeringDB | |
| IX Australia Brisbane (QLD-IX) Brisbane, Australia | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| IX Australia Perth (WA-IX) Perth, Australia | 10G | Both IPv6 not in PeeringDB | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 100G | Both IPv6 not in PeeringDB | |
| MegaIX Brisbane Brisbane, Australia | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| MegaIX Melbourne Melbourne, Australia | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| MegaIX Perth Perth, Australia | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| MegaIX Sydney Sydney, Australia | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB |
These exchanges have a switch in a facility where Opticomm Pty Ltd lists itself in PeeringDB, but don't have Opticomm Pty Ltd as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| NetIXSofia, Bulgaria | 204 | |
| IX Australia Adelaide (SA-IX)Adelaide, Australia | 39 | |
| EdgeIX - AdelaideAdelaide, Australia | 36 | |
| MegaIX AdelaideAdelaide, Australia | 24 | |
| ixFabricGlobal, Australia | 2 |
Facilities (10)
The buildings Opticomm Pty Ltd lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix SY1/SY2 - SydneySydney | 4 of 5 | |
| DigiCo Adelaide ADL1 (YourDC Ed Parks)Edinburgh Parks | 0 of 4 | |
| DigiCo Sydney SYD1 (formerly Global Switch Australia)Sydney | 3 of 4 | |
| DigiCo Adelaide ADL2 (YourDC Hawthorn)Adelaide | 0 of 3 | |
| NEXTDC B1Brisbane | 3 of 3 | |
| NEXTDC B2Fortitude Valley | 3 of 3 | |
| NEXTDC M1Melbourne | 3 of 3 | |
| NEXTDC P1Málaga | 3 of 3 | |
| NEXTDC P2Perth | 3 of 3 | |
| NEXTDC M2Tullamarine | 2 of 2 |