The Telstra outage that disrupted nearly half of all calls and data sessions across Australia last week was caused by a neglected software update, CEO Vicki Brady told a Senate inquiry. The failure stemmed from a time-keeping server that reset to 2006 after a maintenance shutdown, cascading authentication errors across the network.
What Happened During the Telstra Outage?
On Wednesday, shortly before 4:30am AEST, Telstra's mobile network went down, affecting 45% of all voice calls and data sessions. The root cause was a Microchip SSU 2000 network time protocol (NTP) server in Melbourne. Manufactured in 2011 and costing $30,000 to replace, this server had not received a critical software update despite manufacturer alerts in 2022 and January this year.
Get the #1 Wireless Door Camera
REOLINK Bestseller: 2K Weatherproof Video Doorbell, No Monthly Fees.
During routine maintenance to replace faulty backup power, the server was shut down and restarted. Due to an underlying software configuration, it booted with the date set to 2006. Over the next few hours, the incorrect time rippled across the network, invalidating authentication certificates in other servers and leaving customers intermittently unable to place calls or use data.
Key Findings from the Senate Inquiry
Telstra executives confirmed that redundancy in the network did not prevent the outage. The company has three NTP servers—in Sydney, Melbourne, and Perth—but the design change in how the server reset was unknown to maintenance teams. The inquiry highlighted that a simple software update could have avoided the nationwide chaos.
| Issue | Details |
|---|---|
| Affected Server | Microchip SSU 2000 (manufactured 2011) |
| Root Cause | Neglected software update |
| Impact | 45% of calls/data disrupted |
| Cost to Replace | $30,000 per server |
| Manufacturer Alerts | 2022 and January 2023 |
Lessons for Network Reliability
This incident underscores the importance of proactive software maintenance in critical infrastructure. Telstra's failure to apply a manufacturer-recommended update led to a cascading failure that could have been prevented. Businesses and consumers alike should prioritize regular updates and change management protocols to avoid similar disruptions.
Key Takeaways
- Neglected software updates can cause widespread network outages.
- Redundancy alone does not guarantee protection against configuration errors.
- Manufacturer alerts must be acted upon promptly.
- Maintenance teams need full visibility into system design changes.
- Investing in updates saves millions in downtime and reputation damage.
FAQ
What caused the Telstra network outage?
The outage was caused by a neglected software update on a network time protocol (NTP) server in Melbourne. The server reset to 2006 after maintenance, invalidating authentication certificates across the network.
How many customers were affected by the Telstra outage?
Telstra reported that 45% of all calls and data sessions were affected during the outage, which began before 4:30am AEST last Wednesday.
Could the Telstra outage have been prevented?
Yes. Telstra was alerted by the manufacturer in 2022 and January 2023 about the need for a software update. Had it been applied, the outage may have been avoided.