Following the incident yesterday we've had further issues with slowdowns of our 3rd party database, causing increased API latency and a raised number of 500s for short bursts this evening. The incident appears to be over, but we are continuing to investigate the root cause.