This incident has been resolved.
Mar 15, 17:48 UTC
Most deployments should have normal operations restored.
Mar 15, 16:05 UTC
All capsules have been recreated. We are currently working through each deployment to ensure that the capsule has rejoined its deployment.
Mar 15, 14:52 UTC
Both instances have been brought back online. We are currently recreating capsules for both hosts.
Mar 15, 13:25 UTC
We've been informed by Google Cloud representatives that the underlying local SSD disks in us-east1-d have an availability issue that they are working to identify the root cause and remediate. Thus far, other regions appear unaffected. Until the underlying problem is fixed by Google Cloud, the instances will remain unavailable.
Mar 15, 12:34 UTC
Both instances for gcp-us-east1-data.2.dblayer.com and gcp-us-east1-memory.2.dblayer.com suffered a host error that caused the instance to be terminated by Compute Engine. We are working with Google Cloud to migrate the instance and get the instances back online. All deployments affected by these events should have failed over to secondary nodes. If you any questions please contact email@example.com
Mar 15, 11:55 UTC
In addition to gcp-us-east1-data.2.dblayer.com, we are also investigating gcp-us-east1-memory.2.dblayer.com. No deployments use both of these hosts, so failover capability should be functional.
Mar 15, 11:13 UTC
We are currently investigating a possible outage with gcp-us-east1-data.2.dblayer.com on GCP US East 1. We are working diligently to bring the host and capsules back up. No other hosts are known to be affected by this outage.
Mar 15, 11:03 UTC