Google Cloud Status Dashboard
This page provides status information on the services that are part of Google Cloud Platform. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit cloud.google.com.
Cloud Spanner Incident #20001
We've received a report of an issue with Cloud Spanner.
Incident began at 2020-01-08 17:37 and ended at 2020-01-08 19:10 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Jan 08, 2020 | 19:10 | The issue with Cloud Spanner, where customers are unable to change node count for instances in multi-region configuration "nam3", has been resolved for all affected users as of Wednesday, 2020-01-08 19:08 US/Pacific. We thank you for your patience while we've worked on resolving the issue. |
|
The issue with Cloud Spanner, where customers are unable to change node count for instances in multi-region configuration "nam3", has been resolved for all affected users as of Wednesday, 2020-01-08 19:08 US/Pacific. We thank you for your patience while we've worked on resolving the issue. |
|||
| Jan 08, 2020 | 18:47 | Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2020-01-08 20:39 US/Pacific. Diagnosis: Cannot change node count for instances running in NA nam3 multi-region configuration. Workaround: No workaround is available at the moment. |
|
Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2020-01-08 20:39 US/Pacific. Diagnosis: Cannot change node count for instances running in NA nam3 multi-region configuration. Workaround: No workaround is available at the moment. |
|||
| Jan 08, 2020 | 17:57 | Description: We are experiencing an issue with Cloud Spanner beginning at Wednesday, 2020-01-08 17:37 US/Pacific. Symptoms: Customers that have instances running in North America multi-region configuration "nam3" may experience errors when attempting to either increase or reduce node count. The issue is not affecting the running instances. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2020-01-08 18:56 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Cannot change node count for instances running in NA nam3 multi-region configuration. Workaround: No workaround is available at the moment. |
|
Description: We are experiencing an issue with Cloud Spanner beginning at Wednesday, 2020-01-08 17:37 US/Pacific. Symptoms: Customers that have instances running in North America multi-region configuration "nam3" may experience errors when attempting to either increase or reduce node count. The issue is not affecting the running instances. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2020-01-08 18:56 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Cannot change node count for instances running in NA nam3 multi-region configuration. Workaround: No workaround is available at the moment. |
|||
| Jan 08, 2020 | 17:55 | Description: We are experiencing an issue with Cloud Spanner beginning at Wednesday, 2020-01-08 17:37 US/Pacific. Symptoms: Customers that have instances running in North America multi-region configuration "nam3" may experience errors when attempting to either increase or reduce node count. The issue is not affecting the running instances. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2020-01-08 18:56 US/Pacific with current details. We apologize to all who are affected by the disruption. |
|
Description: We are experiencing an issue with Cloud Spanner beginning at Wednesday, 2020-01-08 17:37 US/Pacific. Symptoms: Customers that have instances running in North America multi-region configuration "nam3" may experience errors when attempting to either increase or reduce node count. The issue is not affecting the running instances. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2020-01-08 18:56 US/Pacific with current details. We apologize to all who are affected by the disruption. |
|||