Telstra executives have told a Senate inquiry that a national triple zero outage on Wednesday, 15 July 2026, which lasted approximately five hours, could have been prevented if the company had replaced a 15-year-old server or applied a software update that was never installed (The Guardian, 17 July 2026).

CEO Vicki Brady and Gerard Tracey, Telstra's executive for end-to-end resilience, testified before the Environment and Communications References Committee on Friday, 17 July 2026, as part of its inquiry into triple zero service outages (The Guardian, 17 July 2026; ABC News, 17 July 2026). The inquiry was referred on 28 October 2025, with submissions closing 25 November 2025. The committee was granted an extension on 23 March 2026 to report by 14 April 2026.

Brady told the inquiry the outage could have been avoided had Telstra updated its software or properly documented design changes to the affected server. Tracey was more specific about the hardware. "A newer piece of hardware operating in the same design that we intended to, the issue wouldn't have happened," he said. The server in question cost roughly $30,000 to replace (The Guardian, 17 July 2026).

Telstra's own figures, presented at the hearing, show 58,835 triple zero calls were successfully connected during the outage and 604 calls experienced an error (The Guardian, 17 July 2026). The outage disrupted services nationally and cut hundreds of people from triple zero (The Guardian, 17 July 2026).

Two failures sit behind the admission. First, a software update was never applied to the device that triggered the outage, according to Telstra's submission to the inquiry (SMH, 17 July 2026). Second, design changes to the server went undocumented. Brady's opening statement, published on Telstra's Exchange blog on 9 July 2026, foreshadowed the admissions (Telstra Exchange, 9 July 2026).

This is not the first time the committee has heard evidence on triple zero failures. A firewall upgrade to the Optus network triggered an outage on 18 September that prevented over 600 triple zero calls from connecting. Samsung Electronics Australia also gave evidence to the committee at a hearing on 9 December 2025.

The broader context here is that the inquiry is examining systemic resilience of emergency call services across multiple carriers, not a single company's bad day. Two separate outages, two different root causes, the same result: Australians dialling triple zero and not getting through. The Optus failure was a network firewall upgrade gone wrong. The Telstra failure was a geriatric server that a $30,000 replacement and a routine software update would have addressed. Neither cause is exotic. Both are squarely in the territory of ordinary asset lifecycle management and change control, the kind of unglamorous engineering hygiene that doesn't make strategy decks but keeps critical infrastructure running.

For a carrier operating emergency services infrastructure, a 15-year-old server in a critical path is a decision in itself. Telstra's controls around documentation of design changes clearly failed. Brady said as much, in effect, by listing the two things that would have prevented the outage, both internal process failures. The 604 calls that failed to connect each represent someone in an emergency who could not reach help. Whether that translates into regulatory action or further consequences for Telstra is a matter for the committee's final report and the government's response.

The committee has now heard from both major carriers involved in triple zero outages. Its findings will test whether the current framework of carrier self-management of emergency infrastructure resilience is adequate, or whether the Senate recommends harder obligations on asset renewal and change documentation for services that Australians are told will always be there when they pick up the phone.