Service Health
Incident affecting Google Cloud SQL
Cloud SQL instance creation in zones us-central1-c, us-east1-c, asia-northeast1-a, asia-east1-b, us-central1-f may be failing.
Incident began at 2017-02-28 11:45 and ended at 2017-03-03 00:05 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 2 Mar 2017 | 21:47 PST | The issue should have been mitigated for all zones, except us-central1-c. Creating new Cloud SQL 2nd generation instances in us-central1-c still have an issue. Workaround is to create your instances in a different zone. |
| 2 Mar 2017 | 18:55 PST | Correction: Attempts to create new Cloud SQL instances in zones us-central1-c, us-east1-c, asia-northeast1-a, asia-east1-b, us-central1-f may be intermittently failing. New instances affected in these zones will show a status of "Failed to create". Users will not incur charges for instances that failed to create; these instances can be safely deleted. |
| 2 Mar 2017 | 15:51 PST | Attempts to create new Cloud SQL instances in zones us-central1-c and asia-east1-c are failing. New instances created in these zones will show a status of "Failed to create". Users will not incur charges for instances that failed to create; these instances can be safely deleted. |
- All times are US/Pacific