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.
Google Cloud SQL Incident #19004
We've received a report of an issue with Cloud SQL.
Incident began at 2019-09-04 07:04 and ended at 2019-09-04 12:42 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Sep 04, 2019 | 12:42 | The issue with some Cloud SQL databases becoming stuck has been resolved for all affected projects as of Wednesday, 2019-09-04 12:39 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. |
|
The issue with some Cloud SQL databases becoming stuck has been resolved for all affected projects as of Wednesday, 2019-09-04 12:39 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. |
|||
| Sep 04, 2019 | 11:54 | Description: The issue with some Cloud SQL databases becoming stuck after recent changes were applied should be resolved for the majority of users and we expect a full resolution within the next hour. We will provide another status update by Wednesday, 2019-09-04 13:00 US/Pacific with current details. Diagnosis: Cloud SQL databases becoming stuck and showing an "unknown error". Workaround: None at this time |
|
Description: The issue with some Cloud SQL databases becoming stuck after recent changes were applied should be resolved for the majority of users and we expect a full resolution within the next hour. We will provide another status update by Wednesday, 2019-09-04 13:00 US/Pacific with current details. Diagnosis: Cloud SQL databases becoming stuck and showing an "unknown error". Workaround: None at this time |
|||
| Sep 04, 2019 | 09:22 | Description: Our engineering team is still in progress with applying a mitigation. We will provide another status update by Wednesday, 2019-09-04 12:00 US/Pacific with current details. Diagnosis: None at this time Workaround: None at this time |
|
Description: Our engineering team is still in progress with applying a mitigation. We will provide another status update by Wednesday, 2019-09-04 12:00 US/Pacific with current details. Diagnosis: None at this time Workaround: None at this time |
|||
| Sep 04, 2019 | 08:04 | Description: Following investigation, we believe we have found a mitigation for this issue. Our engineering team will apply this mitigation shortly. We will provide another status update by Wednesday, 2019-09-04 09:15 US/Pacific with current details. Diagnosis: None at this time Workaround: None at this time |
|
Description: Following investigation, we believe we have found a mitigation for this issue. Our engineering team will apply this mitigation shortly. We will provide another status update by Wednesday, 2019-09-04 09:15 US/Pacific with current details. Diagnosis: None at this time Workaround: None at this time |
|||
| Sep 04, 2019 | 07:24 | Description: We've received a report of an issue with Cloud SQL following the latest roll out as of Wednesday, 2019-09-04 07:04 US/Pacific. Some databases are not coming back to serving after changes have been applied. We will provide more information by Wednesday, 2019-09-04 08:00 US/Pacific. Diagnosis: None at this time Workaround: None at this time |
|
Description: We've received a report of an issue with Cloud SQL following the latest roll out as of Wednesday, 2019-09-04 07:04 US/Pacific. Some databases are not coming back to serving after changes have been applied. We will provide more information by Wednesday, 2019-09-04 08:00 US/Pacific. Diagnosis: None at this time Workaround: None at this time |
|||