The short version
Key points
- A Telstra network time server restarted believing it was November 2006 instead of 2026.
- The incorrect date affected authentication, security certificates and connections across parts of the mobile network.
- Most mobile calls and data were restored by about 9:30 am, with the main outage mostly resolved by 4 pm.
- A related issue continued to affect some calls, including triple zero, until Thursday afternoon.
- Telstra reported 58,835 successful triple-zero calls and 604 that received an error during the incident.
How the outage began
The outage followed maintenance on one of Telstra’s three network time protocol servers. These systems help keep the mobile network synchronised. Telstra has servers in Melbourne, Sydney and Perth.
The Melbourne server was taken offline for maintenance and then restarted with an underlying software configuration problem. When it came back online, it believed the date was in November 2006. The Sydney and Perth services had continued operating correctly while Melbourne was offline.
The problem began when the incorrect server rejoined the network and started supplying the wrong date. Downstream systems accepted that information, allowing the error to spread through parts of the network.
Why the wrong date caused wider failures
Mobile networks rely on accurate time for synchronisation, equipment authentication and checking whether security certificates are valid. A device or service operating in 2026 can reject a certificate or connection that appears to come from 2006, or otherwise falls outside the expected time window.
As these checks failed, some customers could not authenticate to the network and phones displayed no service. The outage affected mobile calls and data, but its consequences extended to systems that rely on mobile connectivity for normal operation.
Telstra has acknowledged that an earlier design change to the equipment was not properly documented. Maintenance workers therefore did not know how the server would behave after restarting. A software update that may have prevented the failure had also not been installed.
Services affected across Australia
Most calls and data were working again by about 9:30 am, and the main outage was mostly resolved by 4 pm. However, a second issue linked to the same defect continued affecting some calls until a fix was installed at about 1:30 pm on Thursday.
Victoria’s regional V/Line network stopped, while trains in New South Wales were disrupted and freight operations paused because drivers could not reliably communicate with network control. V/Line had moved essential communications to Telstra’s 4G network following the 3G shutdown, and its satellite backup was also affected.
The outage also disrupted taxi payments, café sales and some EFTPOS terminals. Traffic-management systems and court matters were affected. The ABC reported that one family lost readings from a child’s continuous glucose monitor, while some electric-vehicle drivers could not use connected chargers.
Triple zero and the emergency response
The central triple-zero platform did not shut down, and fixed-line calls over the NBN were not affected. Connected calls continued reaching emergency call centres and being passed to state services. The problem was that some Telstra mobile customers could not connect to the emergency system in the first place.
Phones are intended to use another available network for emergency calls when their own carrier is unavailable. That worked for some people, but not everyone. Telstra advised affected users to retry for up to 90 seconds or use another phone.
Telstra told a Senate inquiry that 58,835 triple-zero calls connected successfully during the incident, while 604 received an error. Telstra also reported completing 604 welfare checks, with 427 people confirming they did not need help and 177 referred for further checks or assistance. A claim that the outage contributed to a death in regional South Australia was rejected by South Australian Police, which said the relevant Telstra calls, including the triple-zero call that brought an ambulance, connected successfully.
Investigation and compensation
The Australian Communications and Media Authority is investigating whether Telstra met its emergency-call and outage obligations. The transcript says potential penalties could reach $30 million. Telstra CEO Vicki Brady appeared before a Senate inquiry, apologised and said the company accepted full accountability.
Compensation is being considered case by case. The Telecommunications Industry Ombudsman is advising affected businesses to complain to Telstra first and document their losses. Victoria has promised reimbursements and free V/Line travel while seeking Telstra’s help with those costs.
The key accountability questions concern why the Melbourne server was allowed to rejoin the network with the wrong date, why other systems accepted that information, why the design change was not documented and why relevant software updates had not been completed.
TechManPat’s conclusion
I think this outage shows that redundancy is not enough if a faulty system can rejoin the network and have its incorrect information accepted. Mobile connectivity now supports transport, payments, health devices and emergency access, so Telstra needed stronger controls around a known timing dependency and a routine maintenance restart.
This knowledge-centre summary is based on the linked TechManPat video and reflects the information available when it was published. Check current pricing, availability and policies before acting.
