Telstra Rejects Wells' Criticism Over Outage Alert as Software Bug Exposed 600 Triple Zero Calls Failed, Minister Left in the Dark for 2.5 Hours

Telstra has rejected Communications Minister Anika Wells' criticism over its outage notification process, insisting it met its obligations despite a 2.5-hour delay in alerting her office. The company revealed the outage was caused by a software time-keeping glitch that reset servers' clocks back 20 years , with 639 welfare checks conducted after 600 Triple Zero calls failed .

A major Telstra outage on Wednesday caused chaos across Australia, leaving millions without mobile services, grounding regional trains, and disrupting payment systems. As the dust settles, a political stoush has erupted over how long it took to notify the government.

The telecommunications giant detected problems at 4.30am on Wednesday, but Communications Minister Anika Wells was not informed until about 7am a delay of 2.5 hours. Telstra had already posted an online brief for reporters at 6.35am before directly notifying the minister's office.

When pressed on why media were informed before the minister, Telstra Chief Financial Officer Michael Ackland defended the company's process, stating, "We will always communicate with customers first when we see that there is an issue, and there are certain thresholds in terms of when our obligations are to communicate with everyone." He insisted the government was informed "very, very early" in the morning.

"I would have liked to have heard earlier," Wells said, confirming the delay would form part of the Australian Communications and Media Authority investigation.

The cause of the outage has been identified as a software timing glitch that reset servers' internal clocks back 20 years to November 2006. The defect affected nodes responsible for time synchronization across the mobile network, disrupting authentication processes and preventing customers' phones from connecting.

"One missed call is unacceptable," Ackland said, confirming more than 600 Triple Zero calls failed during the outage. Despite approximately 33,000 emergency calls successfully reaching services, Telstra conducted 639 welfare checks, referring 170 cases to police for further assistance, with seven callers requiring immediate help.

A "secondary issue" affecting Triple Zero calls persisted even after the initial outage was resolved, requiring engineers to work through the night to implement a solution. The frequency of Triple Zero call errors has now been reduced by approximately 90 per cent.

The outage also halted Victoria's entire regional V/Line train network and affected New South Wales regional services, while payment systems for about 80,000 businesses using Tyro were disrupted. Telstra confirmed it was "not the result of a cyber incident."

Liberal Senator Sarah Henderson sparked further controversy by admitting she called Triple Zero to "test" the system, refusing to apologise and saying, "I'm not going to apologise for doing my job.” Her actions were criticised by Labor ministers.

Here is the question this outage raises. A software time-keeping glitch reset a server to 2006 and disrupted the nation for hours. When the problem was detected at 4.30am but the minister was not informed until 7am, and 600 emergency calls failed, is the delay a breach of trust or just a communications failure between two parties who should have been speaking earlier?

As the ACMA investigates Telstra's third major outage in a year, The Silicon Review asks a final question. When Australia's largest telco can be brought to its knees by a software defect and the minister in charge says the industry is already "the least trusted”, who is responsible for ensuring the network that carries emergency calls, is truly resilient?

FAQ:

Q: What caused the Telstra outage on July 8, 2026?
A: Telstra confirmed the outage was caused by a software defect in time-keeping servers at data centres in Sydney and Melbourne. A firmware glitch reset the servers' internal clocks back 20 years, disrupting time synchronization critical for mobile connectivity.

Q: How many Triple Zero calls failed during the Telstra outage?
A: More than 600 Triple Zero calls failed to connect during the outage, despite approximately 33,000 emergency calls successfully reaching services.

Q: Did Telstra conduct welfare checks for Triple Zero call failures?
A: Yes, Telstra conducted 639 welfare checks. Of those, 402 required follow-up calls, 170 were referred to police, and seven callers confirmed they needed help.

Q: Did the Telstra outage affect public transport?
A: Yes. Victoria's entire regional V/Line train network was suspended and regional train services in New South Wales were also affected due to disruptions to signalling systems.

Q: Was the Telstra outage a cyber attack?
A: No. Telstra CFO Michael Ackland confirmed the outage "was not the result of a cyber incident."