So it turns out that the cause was indeed a rogue change they couldn’t roll back as we had been speculating.
Weird that whatever this issue is didn’t occur in their test environment before they deployed into Production. I wonder why that is.
This is the best summary I could come up with:
Optus says “changes to routing information” after a “routine software upgrade” was behind last week’s nationwide outage, affecting 10.2 million Australians and impacting 400,000 businesses.
“These routing information changes propagated through multiple layers in our network and exceeded preset safety levels on key routers which could not handle these,” the company said.
Before Monday’s disclosure by Optus, experts had theorised the outage was likely a “regular software upgrade gone wrong”.
“The problem is too widespread to be due to a cable break or equipment failure,” said Tom Worthington, a senior lecturer in computer science from the Australian National University in Canberra.
The software upgrade theory surmised by telecommunications analysts and experts last Wednesday were put to Optus CEO Kelly Bayer Rosmarin, who rejected those suggestions.
The reason for the outage follows the federal government announcing earlier on Monday that it would require telecommunications companies in Australia to report their cybersecurity measures to avoid a repeat of Optus’ cyber hack last year.
The original article contains 528 words, the summary contains 159 words. Saved 70%. I’m a bot and I’m open source!
It’s as if they were running Windows 10 Home on their servers and had an upgrade forced onto them
Change Manager who approved this is gonna be sweating bullets lol
“Let’s take a look at the change request. Now, see here, this section for Contingencies and Rollback process? Why is it blank?”
All companies have a test environment. Some companies are lucky enough to have a separate environment for production.
This happens in my business all the time…the test FTP IP address is left in the code and shit falls apart costing us millions… They hold a PIR and then it happens again.
