Service Health
-
-
-
-
Incident affecting Google Cloud SQL
Cloud SQL V2 instance failing to create
Incident began at 2017-06-29 08:45 and ended at 2017-06-29 12:00 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| | 29 Jun 2017 | 12:09 PDT | The issue with Cloud SQL V2 incorrect reports of 'Unable to Failover' state has been resolved for all affected instances as of 12:00 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. |
| | 29 Jun 2017 | 11:26 PDT | The issue with Cloud SQL V2 incorrect reports of 'Unable to Failover' state should be resolved for some of instances and we expect a full resolution in the near future. We will provide another status update by 12:30 US/Pacific with current details. |
| | 29 Jun 2017 | 10:55 PDT | Our Engineering Team believes they have identified the root cause of the incorrect reports of 'Unable to Failover' state and is working to mitigate. We will provide another status update by 12:00 US/Pacific with current details. |
| | 29 Jun 2017 | 10:16 PDT | The issue with Cloud SQL V2 some instance maybe failing to create should be resolved for some of porojects and we expect a full resolution in the near future. At this time we do not have additional information related to HA instances may report incorrect 'Unable to Failover' state. We will provide another status update by 11:00 US/Pacific with current details. |
| | 29 Jun 2017 | 09:51 PDT | We are experiencing an issue with Cloud SQL V2, some instance maybe failing to create or HA instances may reports incorrect 'Unable to Failover' state beginning at Thursday, 2016-06-29 08:45 US/Pacific. For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide an update by 11:00 US/Pacific with current details. |
- All times are US/Pacific