Update - (Updating components)
The team is monitoring writes, and full service seems to have been restored for writes. The team continues to re-enable services necessary for reads, and expects to recover for reads within hours. The team does not have a more precise ETA for recovering reads yet, but will update when they have more data.
Sep 17, 17:23 UTC

Update - The team is monitoring writes, and full service seems to have been restored for writes. The team continues to re-enable services necessary for reads, and expects to recover for reads within hours. The team does not have a more precise ETA for recovering reads yet, but will update when they have more data.
Sep 17, 16:49 UTC

Update - Write availability has been restored. Customers should not see any further errors on the write path.

We are beginning the process of restoring read availability. This will involve provisioning further resources and will take some time. We won't restore read availability until we are confident writes are available.
Sep 17, 15:50 UTC

Update - We are finalising the provision of resources necessary to completely restore write availability. We expect this to be completed very soon. Reads remain unavailable on the cluster and the team is working to provision all resources necessary to fully restore read availability
Sep 17, 15:35 UTC

Update - The team continues to implement the recovery process. Currently, they estimate that write availability will be recovered in the next 2 hours, though please be advised this is only their best good faith estimate. We expect read availability to be restored after write availability. The team expects that will take hours as well, but does not have a more specific estimate at this time.
Sep 17, 15:02 UTC

Update - The team continues to make progress restoring service. However, they are still unable to supply an updated estimate for full system recovery. They still anticipate it will be measured in hours.
Sep 17, 14:29 UTC

Update - The team continues to make progress restoring service. However, they are still unable to supply an updated estimate for full system recovery. They still anticipate it will be measured in hours.
Sep 17, 13:51 UTC

Update - aws-eu-central region is still down. The team is making progress, The current plan is that writes will be back online before reads will be available. We have re-confirmed that there does not appear to be any data loss
Sep 17, 12:57 UTC

Update - aws-eu-central region is still down. The team is making progress, but we don't have an updated estimate for when service will be restored yet. We have re-confirmed that there does not appear to be any data loss.
Sep 17, 12:46 UTC

Update - A configuration/operator error caused all compute in our aws-eu-central to be disabled. This incident is limited only to aws-eu-central. Data that has already been written is safe. The engineering team is working on restoring functionality to the cluster. Unfortunately, current estimates for downtime during recovered is measured in hours. We will continue to update as our estimates improve
Sep 17, 12:09 UTC

Update - The cluster is down and we are working on it to resolve the issue
Sep 17, 11:15 UTC

Update - The cluster is down and we are working on it to resolve the issue
Sep 17, 11:00 UTC

Update - We are continuing to investigate this issue.
Sep 17, 10:49 UTC

Update - We are continuing our investigation into this incident and are monitoring for further issues.
Sep 7, 19:58 UTC

Update - We are continuing to monitor for any further issues.
Sep 7, 12:19 UTC

Update - Our team has made changes and we are actively monitoring the situation.
Sep 7, 08:36 UTC