Service Health
Incident affecting Google Cloud SQL
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 | |
---|---|---|---|
| 4 Sep 2019 | 12:42 PDT | 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. |
| 4 Sep 2019 | 11:54 PDT | 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 |
| 4 Sep 2019 | 09:22 PDT | 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 |
| 4 Sep 2019 | 08:04 PDT | 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 |
| 4 Sep 2019 | 07:24 PDT | 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 |
- All times are US/Pacific