Backend cache server connection pooling
We saw an unusual bug yesterday evening where one customer status page was not correctly flushed from our CDN cache when a notice was updated.
Whilst it has been difficult to pin down the exact cause it was noted that the way we manage connections to our backend cache server could be improved.
This afternoon we have rolled out a small patch that improves this, ensuring all our backend processes now use a shared connection pool to the cache servers, making them more reliable.
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.