Subsea Cable Landings in Perth and Sydney: Gateways to Indo-Pacific Interconnection

The landing is not the endpoint

A submarine system becomes useful to a customer through landing infrastructure, shore equipment, inland transport and data-centre interconnection. Perth is an important gateway toward Indian Ocean and Asian routes; Sydney connects major domestic and international ecosystems. A location on a cable map does not identify every intermediate dependency in a purchased circuit.

SUBCO describes INDIGO West as a Perth–Singapore system and INDIGO Central as a Perth–Sydney system. These names provide concrete route context, but an enterprise must ask its carrier which capacity and inland paths actually underpin its service. A advertised presence in both cities is not proof of end-to-end diversity.

Examine the shared-risk chain

A beach manhole, landing station, power system or inland duct can be a common failure point for otherwise separate services. Ask whether the proposed backup uses distinct landing facilities and separate building entries at the customer end. Where full physical disclosure is unavailable, request a carrier statement of shared-risk assumptions and restoration commitments.

Some services switch automatically to a geographically longer route. Applications may remain reachable but experience higher delay or lower throughput. Include those states in replication and disaster-recovery planning.

Build an acceptance record

Document demarcation ports, VLANs, optical levels, committed capacity and escalation contacts. Test traffic between the intended data centres rather than a nearby public speed-test server. Compare normal and backup route behaviour and keep baseline latency and loss data.

Plan for a regional event

Reserve enough alternate capacity for critical applications, with an explicit policy for deferring bulk transfers. A satellite backup can restore local access during a terrestrial fault, but its onward gateway may still depend on the same international region. Trace the application all the way to its hosting location before calling the architecture independent.

From concept to acceptance

Worked design exercise

A customer buys two services terminating in the same Sydney data centre. One reaches Perth through an east–west system and the other follows a different backbone, but both enter the customer building through the same duct. The building entry remains a single point of failure even if the long-haul paths are diverse.

Draw the route at three levels: international or inter-capital transport, metro access and premises entry. Obtain evidence for each claimed separation. A resilience design should state which risks remain shared rather than simply marking both carrier logos as independent.