Current policyReclaim our infrastructureBuild the Network

No Single Points of Failure

Melbourne's rail network has no redundancy: when a single Telstra network fault halted every V/Line train in the state on 8 July 2026, there was no backup for passengers to fall back on. Singapore runs three separate lines through its busiest corridor for exactly this reason. Legislate a redundancy standard for new transit investment, and apply the same principle to bus corridors by pairing route staggering with built-in route overlap.

Adopted byFusion VictoriaApplies toFusion VictoriaIn force since22 July 2026
Sign in to propose a changeAmend, replace or repeal this policy through a member proposal.

Adopted by the Fusion Victoria executive before this record was imported into Engage. Source: the original published policy ↗.

Key commitments
  • No backup when V/Line goes down
  • Singapore builds redundancy into its busiest corridor
  • Redundant bus routes let you stagger for free
  • A planning standard, not a blank cheque
Policy detail

On 8 July 2026, one Telstra network fault took down every V/Line train in the state at once. Victoria's rail network has no backup route, because nobody designed one in.

Melbourne's rail network has no redundancy: when a single Telstra network fault halted every V/Line train in the state on 8 July 2026, there was no backup for passengers to fall back on. Singapore runs three separate lines through its busiest corridor for exactly this reason. Legislate a redundancy standard for new transit investment, and apply the same principle to bus corridors by pairing route staggering with built-in route overlap.

What it does

  • No backup when V/Line goes down — On 8 July 2026, a single Telstra network fault halted every V/Line train in Victoria at once. One point of failure in one telco's network stopped the entire regional rail system, because no part of it has an independent fallback.
  • Singapore builds redundancy into its busiest corridor — The East-West Line, Thomson-East Coast Line and Downtown Line all run through Singapore's highest-patronage eastern approach into the CBD. If one line fails, the others still carry passengers.
  • Redundant bus routes let you stagger for free — Where two or more bus routes already cover the same corridor, staggering them (see Stagger the Timetables) turns overlapping coverage into a high-frequency spine, without needing any single route to independently run turn-up-and-go frequency.
  • A planning standard, not a blank cheque — This mandates that new transit investment be assessed for single points of failure. It directs where the redundancy principle applies rather than committing to a specific, costed build.

Design Rationale

Redundancy is standard practice in mature, high-patronage transit networks, because a single line or single dependency failing shouldn't strand an entire corridor. Singapore runs three separate lines, the East-West Line, Thomson-East Coast Line and Downtown Line, through its highest-patronage eastern approach into the CBD for exactly this reason: relief and fallback capacity if any one line has a problem. Victoria's regional rail network has the opposite design. V/Line's entire signalling and communications system depends on a single telco's mobile network, and the 8 July 2026 outage proved that a fault at that single point can halt every train in the state simultaneously. The same principle applies to bus corridors at much lower cost: where two or more routes already cover overlapping ground, that overlap is redundancy that can be actively used, not wasted. Staggering redundant routes, the mechanism specified in Stagger the Timetables, converts route overlap into a de facto high-frequency spine, without requiring any single route to be funded at turn-up-and-go frequency on its own.

System Interaction

V/Line's signalling and train communications currently depend on commercial telco infrastructure with no independent backup, the exact dependency that failed on 8 July 2026. A redundancy standard would require DTP to assess and disclose single points of failure (telco dependency, single-corridor rail alignments, single-operator bus contracts) for major existing and future transit investment. Applying route redundancy to bus corridors interacts directly with the timetable-staggering mechanism in Stagger the Timetables: DTP's existing timetable-setting process would need to treat overlapping routes as a frequency asset to be coordinated, not scheduled independently.

Economic & Institutional Logic

Redundancy has an upfront cost, parallel infrastructure, backup communications systems, but an avoided cost that's easy to underweight until a failure makes it concrete. The 8 July 2026 outage stranded passengers statewide for the duration of the fault, at a cost to commuters and the state's reliability reputation that a backup communications path would have avoided. On buses, the economics are better than on rail: redundant routes are frequently already funded and running, so the only additional cost is the scheduling coordination Stagger the Timetables already specifies, not new capital.

Risk & Failure Modes

The main risk is treating this as a one-off response to the July outage rather than a standing planning standard. Without a legislated requirement to assess single points of failure, the same dependency, or an equivalent one, can simply be rebuilt into the network's next generation of infrastructure. On the bus side, coordinating staggered, redundant routes requires the same ongoing DTP compliance discipline as Stagger the Timetables, and carries the same risk of being treated as a one-off audit rather than a standing check.

Evidence & Precedent

The 8 July 2026 Telstra network outage halted every V/Line service in Victoria simultaneously, a documented, dated, statewide failure directly attributable to a single point of failure in train communications infrastructure. Singapore's Thomson-East Coast Line was explicitly built to relieve and provide redundancy for the East-West and North-South Lines on the country's busiest travel corridor, and is being extended to interchange with the Downtown Line, giving that corridor three independent lines. This is an operating, delivered example of the redundancy principle this policy asks Victoria to adopt, not a hypothetical.

Implementation Outline

Sequence 1: Legislate a requirement for DTP to assess and publicly disclose single points of failure (telco dependency, single-corridor alignments, single-operator contracts) in current transit infrastructure, starting with the V/Line train communications dependency exposed by the July 2026 outage. Sequence 2: Require new major transit investment business cases to include a redundancy assessment before funding approval. Sequence 3: Direct DTP to identify existing bus corridors with overlapping, redundant routes and apply the Stagger the Timetables mechanism to convert that overlap into coordinated high-frequency spines. Sequence 4: Commission a business case for backup train communications infrastructure independent of a single telco provider.

What it costs

Audits and backup systems require project-level costing

Paid for by

Cost communications redundancy and route alternatives after identifying failure points. Legislation alone does not deliver backup capacity.

Imported wording revision: rev-vic-no-single-points-of-failure-17965a2eb53b

Adoption record and sources
Policy identifier
vic-no-single-points-of-failure
How it was adopted
Imported from Imported from Fusion Party Victoria; adopted by the branch executive.
Source proposal
No source proposal recorded.
Ballot result
No Engage ballot recorded
Authority
Fusion Victoria
Decision event
Not recorded
Ratified
Not ratified through Engage
Effective
22 July 2026
Published
15 November 2026
Provenance
Imported from Fusion Party Victoria
Import basis
Adopted by the Victorian branch executive. Confirmed by the Engage maintainer on 2026-11-15 that all live Victorian branch policies are ratified and adopted.
Imported
15 November 2026
Source record
no-single-points-of-failure
Adopted amendments
None recorded
Published wording revisions
rev-vic-no-single-points-of-failure-17965a2eb53b
← Fusion Victoria policy