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.

You are viewing a single thread.
View all comments View context
4 points

how else do you explain to the layman “catastrophic failure in the configuration update of core network infrastructure and its preceding, meant-to-be-soundproof, processes”

permalink
report
parent
reply

Australia

!australia@aussie.zone

Create post

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:

  • When posting news articles use the source headline and place your commentary in a separate comment
Banner Photo

Congratulations to @Tau@aussie.zone 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: @lodion@aussie.zone and @Nath@aussie.zone

Community stats

  • 1.3K

    Monthly active users

  • 1.5K

    Posts

  • 15K

    Comments