Fixed a rare bug where components were incorrectly showing as degraded
A customer reported a bug yesterday, in which one of their components continued to show as degraded despite them having marked the notice as resolved.
After some rigorous debugging, we determined that this was likely due to a race condition that was causing the old state of the component to be re-cached, rather than picking up the new state after a customer marked the notice as resolved.
We have today released a patch that prevents this condition from occurring.
Find Your Subscription
We’ll find your subscription and send you a link to login to manage your preferences.
Check Your Inbox
We’ve found your existing subscription and have emailed you a secure link to manage your preferences.
Subscribe to Status Updates
We’ll use your email to save your preferences so you can update them later.
-
Email{{ value }}
-
Text Message{{ value }}
-
Slack
-
Microsoft Teams{{ value }}
-
Google Chat
Subscribe to other services using the bell icon on the subscribe button on the status page.
Unsubscribe Completely?
You’ll no long receive any status updates from Sorry™ Service Status, are you sure?
{{ error }}
You’re Unsubscribed!
We’ll no longer send you any status updates about Sorry™ Service Status.