The errors appear to have been caused by one of the tables In our database, which is used for storing and processing background jobs reaching its limits. The limit on this column had to be bumped up to get things moving again.
We've reviewed all tables in the database to ensure we're not likely to run into this issue again.
Thanks as always for your understanding.
Starting at around 00:55 UTC we saw an increase in failed requests to the Management UI and certain API requests.
Things look to be running normally again since 01:10 UTC after we made some configuration changes to our database servers. We're now looking more closely at what went wrong.
Some people are experiencing problems with our service right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.
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.