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.

  • zurohki
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    I’m sure there was a rollback process, it just didn’t work.

    • MalReynolds@slrpnk.net
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      If you don’t test a restored backup, you don’t have a backup, same applies here.