Resolved -
This incident has been resolved.
Jun 10, 09:18 UTC
Monitoring -
We have moved the affected shard to a different node and are replacing the database node in question. Service for affected customers should be resumed.
Jun 10, 08:30 UTC
Identified -
We believe a node in our database is the potential cause of the issue. We're continuing to investigate
Jun 10, 08:18 UTC
Update -
We are continuing to investigate this issue.
Jun 10, 08:14 UTC
Investigating -
A small number of users are reporting a 500 status code in response to requests in the EU-WEST-1 region. We suspect an issue with one of the clusters and are investigating the cause.
Jun 10, 08:14 UTC