This afternoon we released a patch for a bug to spacing between updates on maintenance notices, and swiftly shot ourselves in the foot by introducing a new bug which broke the display of components on some status pages.
This issue was spotted roughly an hour later and the change was rolled back as soon as we knew about it.
It appears the issue slipped through our automated test suite because it wasn't raising a specific error, just silently failing to load the component tree.
Furthermore, because the code change appeared to be unrelated to the component tree it wasn't covered in our manual QA process for this change.
We will now make efforts to improve our test coverage so that it more comprehensively checks the components are correctly loaded.
Sorry for the confusion.
We’ll find your subscription and send you a link to login to manage your preferences.
We’ve found your existing subscription and have emailed you a secure link to manage your preferences.
We’ll use your email to save your preferences so you can update them later.
Subscribe to other services using the bell icon on the subscribe button on the status page.
You’ll no long receive any status updates from Sorry™ Service Status, are you sure?
{{ error }}
We’ll no longer send you any status updates about Sorry™ Service Status.