2 min read

Telstra says 2006 time jump triggered mobile outage

Telstra told a Senate inquiry an NTP server reset to 2006 after maintenance, helping cause a major mobile outage that hit 000 calls.

Image: The Register

Telstra has told an Australian Senate inquiry that a network time server resetting itself to 2006 helped trigger the mobile outage that disrupted its network, including access to Australia’s 000 emergency services line, electronic payments, and transport systems.

In a submission to the inquiry, the carrier said the immediate trigger was maintenance intended to fix a known resilience issue: a faulty backup power feed in the chassis housing a network time protocol (NTP) server. A technician began replacing the chassis a few minutes before midnight on July 7 and finished powering the server back on by 3:38 AM on July 8.

When the server restarted, its GPS card “did not operate as expected,” according to Telstra. The company said it now believes that happened because of an earlier intentional design change made to fix a previous fault, but that change was not properly documented. As a result, the maintenance team did not know how the device would behave after a restart.

Telstra also admitted it had not applied a software update to the device, despite knowing it was available in early 2026.

Recommended reading

FBI eyes Nvidia and Google TPU AI systems

“Had that software update been completed or had the design change been properly reviewed and documented post the earlier incident, and reflected in the maintenance procedure, the outage may not have occurred.”

Telstra submission to the Senate inquiry

Once the NTP server came back online, it began distributing the wrong time across the network. Other systems then compared digital certificates, detected a mismatch, and rejected connections. Only one of Telstra’s three NTP servers was affected, but that was enough to cause widespread disruption.

Telstra said it isolated the faulty server at 7:11 AM, and by 10:30 AM had identified all network components that had consumed the bad time data. But the damage lingered: as correct time spread through the network, some equipment did not close IP sessions, which meant some customer devices could not reconnect unless they were rebooted.

The carrier called the outage “clearly unacceptable” and said the incident exposed weak internal controls around change documentation, software updates, and risk management. The Senate inquiry was originally focused on rival Optus, whose own outage has been linked to multiple deaths after people were unable to reach emergency services.

Marcus Vance

Enterprise Editor

Marcus follows the money. He covers enterprise software, cloud architecture, and the tectonic shifts in Big Tech strategy. He translates dense earnings calls and complex M&A activity into actionable insights about where the industry is actually heading. If a tech giant makes a silent pivot, Marcus is usually the first to notice.

via The Register

// Keep reading