The Telstra network outage that caused nationwide chaos last week was triggered by a neglected software update on a critical time-keeping server, CEO Vicki Brady told a Senate inquiry. The outage affected 45% of all calls and data sessions, leaving millions of Australians without mobile service for hours.
What Caused the Telstra Network Outage?
According to Telstra's submission, one of its three Network Time Protocol (NTP) servers—a Microchip SSU 2000 model manufactured in 2011—reset to 2006 after a maintenance procedure. The server, located in Melbourne, was shut down and restarted during a faulty backup power replacement. Due to an underlying software configuration, it rebooted with the incorrect date.
This error rippled across the network, invalidating authentication certificates in other servers. Customers experienced intermittent "no service" alerts, unable to place voice calls or use mobile data. The outage began shortly before 4:30am AEST last Wednesday and persisted for hours.
Redundancy Did Not Prevent the Failure
Telstra insisted it had network redundancy, but the design change in the server's reset behavior meant that redundancy did not stop the outage. The company admitted its maintenance teams were unaware of this design change, highlighting a gap in operational awareness.
Software Update Warning Ignored
In both 2022 and January this year, the manufacturer alerted Telstra about the need to update the server's software. The Senate inquiry heard that had this update been applied, the outage might have been avoided. The server, still under support from Scientific Devices, costs $30,000 to replace, but the issue was not hardware—it was a neglected software update.
Comparison of Telstra's NTP Servers
| Location | Model | Year Manufactured | Replacement Cost |
|---|---|---|---|
| Sydney | Microchip SSU 2000 | 2011 | $30,000 |
| Melbourne | Microchip SSU 2000 | 2011 | $30,000 |
| Perth | Microchip SSU 2000 | 2011 | $30,000 |
Key Takeaways from the Telstra Outage
- Software updates are critical for network stability and security.
- Redundancy alone cannot compensate for configuration errors in core systems.
- Maintenance teams must be informed of design changes to prevent cascading failures.
- Vendor alerts should be acted upon promptly to avoid costly disruptions.
FAQ
What caused the Telstra network outage?
The outage was caused by a neglected software update on a Network Time Protocol server that reset to 2006, invalidating authentication certificates across the network.
How many customers were affected by the Telstra outage?
Approximately 45% of all calls and data sessions were affected, impacting millions of Telstra mobile customers across Australia.
Could the Telstra outage have been prevented?
Yes, Telstra was alerted by the manufacturer in 2022 and January this year to update the software. Applying the update could have avoided the outage.
Shop premium products at GrandGoldman.com
