We are experiencing an issue with Cloud SQL v1 instance availability in us-central1-a beginning at Thursday, 2018-08-16 08:48 US/Pacific. Our engineering team has identified the problem and is performing mitigation. For everyone who is affected, we apologize for the disruption. We will provide an update by Thursday, 2018-08-16 11:15 US/Pacific with current details.
There is an error log but in the log is not clear if it is caused by this issue:
HttpBadRequestError: HttpError accessing <https://servicecontrol.googleapis.com/v1/services/praktrikcom.appspot.com:report?alt=json>: response: <{'status': '400', 'content-length': '119', 'x-xss-protection': '1; mode=block', 'x-content-type-options': 'nosniff', 'x-goog-trace-id': '123ff47823337dd14fb64f98f3d8498f', 'transfer-encoding': 'chunked', 'vary': 'Origin, X-Origin, Referer', 'server': 'ESF', '-content-encoding': 'gzip', 'cache-control': 'private', 'date': 'Sun, 08 Jul 2018 19:36:16 GMT', 'x-frame-options': 'SAMEORIGIN', 'alt-svc': 'quic=":443"; ma=2592000; v="43,42,41,39,35"', 'content-type': 'application/json; charset=UTF-8'}>, content <{ "error": { "code": 400, "message": "Precondition check failed.", "status": "FAILED_PRECONDITION" } } >
The incident you mentioned was related to the Cloud SQL v1 instance availability in us-central1-a.
If you have such an instance and you are still encountering issues related to this instance, I recommend that you open a PRIVATE case in the Issue Tracker and provide us with your project number and your Cloud SQL instance name so that we would be able to investigate the root cause of the issue efficiently. If not, you may post your full detailed question to Stack Overflow, using the supported Cloud tags for technical question.
- Note that Google Groups are reserved for general Google Cloud Platform-end product discussions and not for reporting issues or technical questions.