A new “secondary issue” was identified at about 9.30pm overnight, several hours after the telco said its original nationwide outage, caused by an issue with timekeeping nodes in Telstra data centres, had been fixed.
This new issue continued to affect Triple Zero calls, but this morning, Telstra said, matters were mostly resolved.
“Overnight, our team have made good progress reducing the occurrence of the subsequent Triple Zero calling error by approx. 90 per cent and will continuing (sic) work to eliminate this issue entirely,” the company said in an update at about 6.30am AEST today.
“Our welfare checks process remains in place, and we continue to advise customers who experience the issue to wait for the call to be connected via an alternative network or recall using a different phone.”
At 10am, the telco issued another statement which potentially indicated issues on the network remained.
Telstra has failed to fully restore Triple Zero access after a five-hour outage, with emergency calls for some Australians still blocked, as a Liberal senator’s claim an elderly person died after failing to contact triple-0 during the outage dubbed “dangerous”
Telstra had a nation-wide network outage last week that affected emergency services.
The outage has been pinned on an obsolete Symmetricom SyncServer S300 node, which manages time on the network but resets its 10-bit week counter to zero every 1024 weeks (just under 20 years) in a common and well understood GPS rollover bug that caused the device to reset to 2006.
The SyncServer S300 was discontinued in 2016.