Telstra's mobile network stopped working across the whole country on 8 July 2026. When engineers finally fixed the main problem, they discovered something worse: some customers who called triple zero (000) — the emergency number — got an error message instead of reaching a real person The Guardian.

Telstra said the first problem was a "software defect" — basically, a mistake in the computer code running part of the network. These faults usually get fixed quickly because modern phone networks rely on precise timing to connect calls, switch between towers, and charge customers. This one didn't work out that way The Guardian.

According to Telstra's own account, the company spotted the second problem — affecting triple-zero calls — around 9:30pm. This was hours after they thought they'd fixed the main fault Nine News.

Here's what actually happened with the emergency calls. When some Telstra customers dialled triple zero, the call failed. Their phone then tried to automatically switch to another carrier's network to go through. Normally, triple-zero calls work no matter which company owns your SIM card — any phone near any network is supposed to reach emergency services. When that automatic handoff broke, it moved from being a phone-network problem into a genuine safety issue The Guardian.

Telstra posted an update on its own blog confirming that some calls, including triple-zero attempts, had been affected Telstra.

Telstra carried out more than 300 welfare checks on people who'd tried to call triple zero during the outage. The company's chief executive, Michael Ackland, suggested some of those calls might have been people simply testing whether the line worked rather than facing a real emergency. That's a reasonable explanation for at least some of the calls — but it doesn't change the fact that 300 welfare checks on the country's biggest phone company in one night isn't normal.

There's also a timing question that will attract attention from regulators. Telstra delayed before telling federal Communications Minister Anika Wells about the outage ABC News. When outages affect emergency call services, how fast a carrier tells the government can become a regulatory investigation months later. That's what will happen here.

The network breakdown caused major problems for trains across two states. NSW Transport warned Sydney Trains and regional services would suffer disruptions. In Victoria, V/Line cut services to a small coach service and asked passengers not to travel if possible. By contrast, the Sydney and Melbourne metro systems kept running without major issues The Guardian.

The difference reflects how regional trains and metro systems work differently. Regional train lines rely much more heavily on mobile data to run signals, keep drivers connected, and display passenger information. Metro systems have more built-in backup methods, so they kept operating when the mobile network failed.

The broader pattern here is familiar. A fault that starts as a small problem in one part of the network cascaded into a much bigger crisis in a different part. A software mistake changing how timing works should have been fixed within an hour with a patch and a rollback. Instead it caused a chain that ended with people unable to reliably call emergency services and two states scrambling to run train networks without mobile connectivity.

The real questions for regulators aren't technical — they're about process and responsibility. Did Telstra follow its own procedures for handling faults that touch emergency services, and did it do so on time? Why did the government only learn about the outage when it did, and does that breach any rule about how quickly the company must report failures involving triple zero? And should V/Line be reviewing how dependent it's become on mobile networks, especially when its backup plan is such a stripped-back coach service? These questions aren't answered yet. They'll come up when Telstra faces questioning from Parliament.