Fixed errors being incorrectly cached by our CDN
Recently, some of our monitoring alerts triggered, indicating the application was offline, despite everything appearing to be operating normally for users.
After conducting a deeper diagnosis, we discovered an unusual set of circumstances where an intermittent error on our origin servers was being incorrectly cached and served for the next 60 minutes.
Whilst we don't believe this impacted customers last week, there was a non-trivial risk that this might cause wider spread problems in the future should it happen again.
Today, we have released a patch that prevents these errors from being cached in this way.
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.