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 comment's thread
view the rest of the comments
[–] 10 points 2 years ago (1 child)

It's as if they were running Windows 10 Home on their servers and had an upgrade forced onto them

  • source
  • hideshow 1 child comment
  • [–] 3 points 2 years ago

    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”

  • source
  • parent