this post was submitted on 23 Jan 2024
13 points (93.3% liked)

Australia

3611 readers
115 users here now

A place to discuss Australia and important Australian issues.

Before you post:

If you're posting anything related to:

If you're posting Australian News (not opinion or discussion pieces) post it to Australian News

Rules

This community is run under the rules of aussie.zone. In addition to those rules:

Banner Photo

Congratulations to @[email protected] who had the most upvoted submission to our banner photo competition

Recommended and Related Communities

Be sure to check out and subscribe to our related communities on aussie.zone:

Plus other communities for sport and major cities.

https://aussie.zone/communities

Moderation

Since Kbin doesn't show Lemmy Moderators, I'll list them here. Also note that Kbin does not distinguish moderator comments.

Additionally, we have our instance admins: @[email protected] and @[email protected]

founded 1 year ago
MODERATORS
 
  • In short: Optus says close to 2,700 customers tried and failed to call emergency services from their mobile phones during the November 2023 network outage.
  • This number is more than 10 times higher than what the telco previously told the Senate.
  • What’s next? Optus says it is writing to each customer individually to apologise, and the federal government is conducting a post-incident review.
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 9 months ago (1 children)

I would imagine they feel pretty shit, especially if people literally died due to the delays caused by not being able to access 000 😬

Imagine if missing a dot in an IP or some other tiny typo caused a cascade effect that resulted in people dying. You'd carry that shit forever, even if technically it wasn't "your" fault directly.

[–] [email protected] 2 points 9 months ago

Any comment I made on the cause of the incident would be pure speculation, but I'd be astonished if it were something so trivial. I suspect it more likely to be through some unknown hardware bug that didn't happen in the Dev/Test environments for some reason. From what they have told the Senate Committee, this was a routine update. Those don't usually carry significant risk of failure.

So all we do know for real is that it was very unexpected and complicated to fix. Something minor like you are describing would not generally take 10 hours to roll back.