Update - We're in the process of restoring expected capacity and working to reduce the amount of throttling currently impacting connections. We should have more information soon.
Dec 8, 06:18 PST

Update - We've started opening the flood-gates and are letting users back in. Recovery is proceeding as planned - and we will continue to ramp up traffic levels and monitor.
Dec 7, 13:36 PST

Update - Google has updated their status page:

> Current data indicates that approximately 0.01% of PD-SSD volumes in us-east1-b are affected by this issue, from a peak of approximately 8.45%.
> At this time, the issue is contained, and we can confirm that this is only impacting us-east1-b.

We are currently beginning to work on service recovery on our end. Please standby!
Dec 7, 13:06 PST

Update - Google's Engineering team continues to work on mitigating the issue, and have posted the following update:

> Mitigation work is currently underway by our engineering team.
> We do not have an ETA for mitigation at this point.

We have all hands on deck awaiting the resolution of this issue to begin restoring service.
Dec 7, 11:58 PST

Update - We continue to observe elevated IO latency. Google has finally gotten to updating their status page. We continue to await resolution.

https://status.cloud.google.com/incident/compute/19012
Dec 7, 11:35 PST

Update - Google is currently investigating an issue with SSD Persistent Disk in our region (what our database clusters store their data on). We are awaiting their resolution.

Given the IO starvation, we are expecting continued API latency - as most if not all of our datastores are currently degraded. We will post updates as we get them.
Dec 7, 10:54 PST