Service Health
-
-
-
-
Incident affecting Google Cloud SQL
Increased latency and possible partial results when listing Cloud SQL instances in us-central1 and us-east1
Incident began at 2021-03-04 10:15 and ended at 2021-03-04 18:27 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| | 4 Mar 2021 | 18:27 PST | The issue with Cloud SQL is believed to be affecting a very small number of projects and our Engineering Team is working on it. If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved. We thank you for your patience while we're working on resolving the issue. |
| | 4 Mar 2021 | 17:15 PST | Description: We believe the issue with Cloud SQL list operations is mitigated and we are monitoring for any reoccurrences. We will provide an update by Thursday, 2021-03-04 18:30 US/Pacific with current details. Diagnosis: Increased latency when listing Cloud SQL instances and/or a warning error "REGION_UNREACHABLE" with partial results. Workaround: None at this time |
| | 4 Mar 2021 | 16:37 PST | Description: Mitigation work is still underway by our engineering team. Our engineering believes to have identified the root cause and is applying a fix. We are monitoring for recovery after fix is applied. We will provide more information by Thursday, 2021-03-04 17:15 US/Pacific. Diagnosis: Increased latency when listing Cloud SQL instances and/or a warning error "REGION_UNREACHABLE" with partial results. Workaround: None at this time |
| | 4 Mar 2021 | 15:01 PST | Description: Mitigation work is currently underway by our engineering team. We are continuing to monitor to verify is this helps decrease latency. We will provide more information by Thursday, 2021-03-04 16:30 US/Pacific. Diagnosis: Increased latency when listing Cloud SQL instances and/or a warning error "REGION_UNREACHABLE" with partial results. Workaround: None at this time |
| | 4 Mar 2021 | 13:38 PST | Description: We are experiencing an issue with Cloud SQL beginning at Tuesday, 2021-03-02 05:30:00 US/Pacific. Listing Cloud SQL instances in regions us-central1 and us-east1 may experience latency and/or a warning error "REGION_UNREACHABLE" with partial results. Other operations that do not rely on .List will continue to work. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2021-03-04 15:00 US/Pacific with current details. Diagnosis: Increased latency when listing Cloud SQL instances and/or a warning error "REGION_UNREACHABLE" with partial results. Workaround: None at this time |
| | 4 Mar 2021 | 11:27 PST | Description: We are experiencing an issue with Cloud SQL beginning at Tuesday, 2021-03-02 05:30:00 US/Pacific. Listing Cloud SQL instances in regions us-central1 and us-east1 may experience latency and/or a warning error "REGION_UNREACHABLE" with partial results. rr Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2021-03-04 13:30 US/Pacific with current details. Diagnosis: Increased latency when listing Cloud SQL instances and/or a warning error "REGION_UNREACHABLE" with partial results. Workaround: None at this time |
| | 4 Mar 2021 | 10:37 PST | Description: We are experiencing an issue with Cloud SQL beginning at Tuesday, 2021-03-02 05:30:00 US/Pacific. Listing Cloud SQL instances in regions us-central1 and us-east1 may experience latency and/or a warning error "REGION_UNREACHABLE" with partial results. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2021-03-04 11:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Increased latency when listing Cloud SQL instances and/or a warning error "REGION_UNREACHABLE" with partial results. Workaround: None at this time |
- All times are US/Pacific