ixreport

Occom

AS135126 · Occom

Occom Pty Ltd

9Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
9Using the route servers
2To fix in PeeringDB
4Facilities in PeeringDB

Tools: Where can I peer with Occom? · Where should Occom peer next? · Compare Occom with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Occom's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Occom'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 (2)

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. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:1:2:fd6:0:1 2001:7fa:11:1:2:fd6:0:2
    • In the entry with IPv4 218.100.78.157: set IPv6 to 2001:7fa:11:1:2:fd6:0:1 (now empty).
    • In the entry with IPv4 218.100.78.61: set IPv6 to 2001:7fa:11:1:2:fd6:0:2 (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. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:4:2:fd6:0:1
    • In the entry with IPv4 218.100.52.220: set IPv6 to 2001:7fa:11:4:2:fd6: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.

Exchanges over time

0246810Oct 3, 2026Nov 19, 20269
Show as a table
DateExchanges
Nov 19, 20269
Nov 18, 20269
Nov 17, 20269
Nov 16, 20269
Nov 15, 20269
Nov 14, 20269
Nov 13, 20269
Nov 12, 20269
Nov 11, 20269
Nov 10, 20269
Nov 9, 20269
Nov 8, 20269
Nov 7, 20269
Nov 6, 20269
Nov 5, 20269
Nov 4, 20269
Nov 3, 20269
Nov 2, 20269
Nov 1, 20269
Oct 31, 20269
Oct 30, 20269
Oct 29, 20269
Oct 28, 20269
Oct 27, 20269
Oct 26, 20269
Oct 25, 20269
Oct 24, 20269
Oct 23, 20269
Oct 22, 20269
Oct 21, 20269
Oct 20, 20269
Oct 19, 20269
Oct 18, 20269
Oct 17, 20269
Oct 16, 20269
Oct 15, 20269
Oct 14, 20269
Oct 13, 20269
Oct 12, 20269
Oct 11, 20269
Oct 10, 20269
Oct 9, 20269
Oct 8, 20269
Oct 7, 20269
Oct 6, 20269
Oct 5, 20269
Oct 4, 20269
Oct 3, 20269

Map

Where Occom'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.

Exchanges

Total port capacity 140G across 9 exchanges.

Australia EdgeIX - Melbourne Melbourne, Australia 202.77.90.69 10G Yes PeeringDB
Australia EdgeIX - Sydney Sydney, Australia 202.77.88.97 10G Yes Both
Australia Equinix Melbourne Melbourne, Australia 183.177.61.42 2001:de8:6:1:0:13:5126:1 10G Yes PeeringDB
Singapore Equinix Singapore Singapore, Singapore 27.111.229.46 2001:de8:4::13:5126:1 10G Yes PeeringDB
Australia Equinix Sydney Sydney, Australia 45.127.172.218 2001:de8:6::13:5126:1 30G Yes PeeringDB
Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia 218.100.78.61
218.100.78.157
2 × 10G Yes Both IPv6 not in PeeringDB
Australia IX Australia Sydney (NSW-IX) Sydney, Australia 218.100.52.220 20G Yes Both IPv6 not in PeeringDB
Australia MegaIX Melbourne Melbourne, Australia 103.26.71.172 2001:dea:0:30::ac 10G Yes Both
Australia MegaIX Sydney Sydney, Australia 103.26.68.176 2001:dea:0:10::b0 20G Yes Both

Exchanges in its buildings that it isn't on (7)

These exchanges have a switch in a facility where Occom lists itself in PeeringDB, but don't have Occom 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.

Facilities (4)

The buildings Occom lists in PeeringDB, and how many of the exchanges in each it's on.

Singapore Equinix SG3 - SingaporeSingapore 1 of 7
Australia Equinix SY4 - SydneySydney 4 of 6
Australia Equinix ME1/ME2 - MelbourneMelbourne 4 of 5
Australia DigiCo Sydney SYD1 (formerly Global Switch Australia)Sydney 3 of 4