ACMA probes Telstra after software defect crashes network

By Zara Kincaid · 2026-07-09

How a time-keeping defect cascaded into a national outage

Telstra's network began failing at approximately 4:30 am AEST on 8 July 2026, when a software defect in the carrier's network time-keeping nodes triggered widespread disruptions to mobile calls and data services across Australia. The defect originated in the nodes responsible for synchronising timing signals across the network, causing a cascade that knocked out voice and data connectivity for customers nationwide.verifiedVerified Source: telstra.com.au^[1] Network time-keeping nodes sit at the foundation of modern mobile infrastructure; when they lose synchronisation, call-routing and data-session management across the whole network can collapse within minutes.

Telstra Chief Financial Officer and Group Executive Michael Ackland said the company had isolated the problem. "Our investigation into the root cause is still underway, but we're confident we've identified a software defect and have been able to isolate it. We'll share further technical detail once the investigation is complete. This was not the result of a cyber incident."^[1] The explicit denial of a cyber incident matters in the current environment, where major outages routinely attract early speculation about malicious causes.

Triple Zero disruptions and the welfare-check process

The outage created a secondary problem for the emergency call system. Some Triple Zero callers received error messages or were automatically routed to alternative networks rather than reaching the Emergency Call Person directly.^[1] Under Australian telecommunications law, carriers must conduct immediate welfare checks when an emergency call fails or is disconnected, and coordinate with police and emergency services when customers cannot connect to Triple Zero.

By 5:30 pm AEST on 8 July 2026, Telstra had completed 395 welfare checks: 167 callers were confirmed safe by SMS, 143 by follow-up call, 79 were referred to police for in-person welfare checks, and 6 required emergency assistance.verifiedVerified Source: telstra.com.au^[1] Those figures show the real-world stakes when an emergency call system degrades; even a relatively brief outage can leave people in genuine danger unable to reach help.

Telstra advised customers experiencing difficulty reaching Triple Zero to immediately retry the call, use an alternative device, or switch to a landline, with its backup welfare-check process remaining active throughout the recovery period.^[1] The Triple Zero core system itself remained operational; the breakdown occurred at the interface between Telstra's carrier network and the Emergency Call Person routing layer.

The test-call controversy

Communications Minister Anika Wells used her public statement to address what she called a serious secondary risk: well-intentioned Australians dialling 000 to check whether the network had recovered. "It is very important that people do not make 'test' calls to Triple Zero, please only call 000 if there is an emergency," Wells said.^[2] The concern is technically grounded; during a degraded network event, test calls consume the same limited routing capacity as genuine emergencies, and each failed test call can trigger an automatic welfare-check obligation, multiplying the load on carriers and emergency services at the same time.

Under the framework overseen by the Triple Zero Custodian, carriers must implement automatic fallback to alternate networks and complete welfare checks for any disconnected emergency call. The 79 police referrals in Telstra's welfare-check tally show how quickly that obligation scales when a large-scale outage intersects with the emergency call system.

Telstra's restoration timeline

Telstra restored 90 per cent of affected mobile calls and data services by 6:30 am AEST on 9 July 2026, approximately 26 hours after the initial fault was identified.verifiedVerified Source: telstra.com.au^[1] Intermittent issues persisted beyond that point, meaning a portion of customers continued to experience degraded service into the morning of 9 July. Telstra said it would release further technical detail on the root cause once its internal investigation concluded.

Telstra told customers throughout the recovery period to retry any failed call, including to Triple Zero, and confirmed that its welfare-check infrastructure remained operational as services were progressively restored.^[1] The phased restoration approach reflects standard practice when time-synchronisation failures are involved; restoring nodes in sequence avoids re-triggering the cascade that caused the original collapse.

Political and regulatory reaction

Anika Wells said the scale of the disruption demanded a formal regulatory response. "This morning's Telstra outage was widespread and has caused significant disruptions across the country. Telstra has advised that 90 per cent of affected services have been restored however we understand that some intermittent issues persist," Wells said.^[2] Wells confirmed the Australian Communications and Media Authority will conduct a full investigation, with Telstra required to account for how and why the outage occurred.^[2]

The ACMA investigation arrives under a newly strengthened regulatory framework. ACMA introduced new outage-transparency rules in November 2025, which became enforceable on 30 June 2026, just eight days before Telstra's network collapsed. Under those rules, Telstra must publish a register of the resolved outage on its website, making the 8 July 2026 incident one of the first to fall under the new disclosure regime.

Zara Kincaid

Zara Kincaid covers AI, search and digital visibility for Bushletter. She writes with technical precision about how these systems actually work.