Console

Service Health

This page provides status information on the services that are part of Google Cloud. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://cloud.google.com/.

Incident affecting Google Cloud Composer, Google Cloud SQL

Intermittent Cloud Composer creation failures in select regions and elevated error rates during Cloud SQL instance creation.

Incident began at 2022-06-30 11:12 and ended at 2022-06-30 19:15 (all times are US/Pacific).

Previously affected location(s)

Taiwan (asia-east1)Hong Kong (asia-east2)Osaka (asia-northeast2)Warsaw (europe-central2)Finland (europe-north1)Frankfurt (europe-west3)South Carolina (us-east1)Los Angeles (us-west2)

Date Time Description
30 Jun 2022 19:15 PDT

We experienced an issue with Google Cloud Composer, Google Cloud SQL beginning at Thursday, 2022-06-28 09:00 US/Pacific.

The issue has been resolved for all affected users as of Thursday, 2022-06-30 19:13 US/Pacific.

We thank you for your patience while we worked on resolving the issue.
30 Jun 2022 17:50 PDT

Summary: Intermittent Cloud Composer creation failures in select regions and elevated error rates during Cloud SQL instance creation.

Description: Mitigation work is underway by our engineering team.

We will provide more information by Thursday, 2022-06-30 20:00 US/Pacific.

Diagnosis: Customers may experience latency and errors with Composer creation. Customer may face errors stating "databases already exist" error upon retrying the creation of Composer.

Customer using Cloud SQL may see failures in calls shortly after database instance creation.

Workaround: Customers may retry the API calls for affected instances while using Cloud SQL.
30 Jun 2022 12:49 PDT

Summary: Intermittent Cloud Composer creation failures in select regions and elevated error rates during Cloud SQL instance creation.

Description: Our engineering team has determined that further investigation is required to mitigate the issue.

We will provide an update by Thursday, 2022-06-30 18:00 US/Pacific with current details.

Diagnosis: Customers may experience latency and errors with Composer creation. Customer may face errors stating "databases already exist" error upon retrying the creation of Composer.

Customer using Cloud SQL may see failures in calls shortly after database instance creation.

Workaround: Customers may retry the API calls for affected instances while using Cloud SQL.
30 Jun 2022 12:04 PDT

Summary: Intermittent Cloud Composer creation failures in select regions and elevated error rates during Cloud SQL instance creation.

Description: Mitigation work is still underway by our engineering team. We will provide more information by Thursday, 2022-06-30 13:00 US/Pacific.

Diagnosis: Customers may experience latency and errors with Composer creation. Customer may face errors stating "databases already exist" error upon retrying the creation of Composer.

Customer using Cloud SQL may see failures in calls shortly after database instance creation.

Workaround: Customers may retry the API calls for affected instances while using Cloud SQL.
30 Jun 2022 11:45 PDT

Summary: Intermittent Cloud Composer creation failures in select regions

Description: Mitigation work is still underway by our engineering team. We will provide more information by Thursday, 2022-06-30 13:00 US/Pacific.

Diagnosis: Customers may experience latency and errors with Composer creation.

Workaround: Customers may retry the Composer creation operation.