I am following up on this morning's incident.
An abnormal amount of traffic was passing through our cache and placing an unexpected load on our origin servers. This was enough to upset our database connection and cause increased request errors and timeouts for around 9 minutes.
Our edge cache and origin shield usually protect us from this kind of issue. However it seems that some malformed requests coming from a particular source were slipping through the net.
We've now made some configuration changes to patch this hole, so it shouldn't cause us any further issues.
We've not seen any further issues with performance or availability so I'm now treating this incident as resolved.
I think we've managed to identify what caused the earlier wobble, but the team continue to work on this so I shall post again once we have a more complete picture.
We saw an increased number of timeouts starting about ten minutes ago at around 11:10 UTC. Things looking to be back to normal for now, but we're digging in to try and find out what caused the initial instability.
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.