Is Cloud Data Fusion down?
Current Cloud Data Fusion status is UP

We checked the official Cloud Data Fusion Status Page 2 min. 0 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Cloud Data Fusion Outages and Issues

Follow the recent outages and downtime for Cloud Data Fusion in the table below.

Start Time

Type

Length

Message

Details

May 16, 2024 23:50 UTC

DOWN

less than a minute

Programming failures for New Virtual Private Cloud endpoints globally affecting New GCE VM network programming and Cloud Run using Direct VPC.

See more
Start Time

May 16, 2024 23:50 UTC

Type DOWN
Affected Components

Americas (regions) - Cloud Data Fusion

Europe (regions) - Cloud Data Fusion

Asia Pacific (regions) - Cloud Data Fusion

Middle East (regions) - Cloud Data Fusion

us-east5 - Cloud Data Fusion

us-south1 - Cloud Data Fusion

us-west1 - Cloud Data Fusion

us-west2 - Cloud Data Fusion

asia-east1 - Cloud Data Fusion

asia-east2 - Cloud Data Fusion

asia-northeast1 - Cloud Data Fusion

asia-northeast2 - Cloud Data Fusion

asia-northeast3 - Cloud Data Fusion

asia-south1 - Cloud Data Fusion

asia-southeast1 - Cloud Data Fusion

asia-southeast2 - Cloud Data Fusion

australia-southeast1 - Cloud Data Fusion

me-west1 - Cloud Data Fusion

europe-north1 - Cloud Data Fusion

europe-west1 - Cloud Data Fusion

europe-west2 - Cloud Data Fusion

europe-west3 - Cloud Data Fusion

us-central1 - Cloud Data Fusion

us-east1 - Cloud Data Fusion

us-east4 - Cloud Data Fusion

northamerica-northeast1 - Cloud Data Fusion

southamerica-east1 - Cloud Data Fusion

europe-west4 - Cloud Data Fusion

europe-west6 - Cloud Data Fusion

Message

Programming failures for New Virtual Private Cloud endpoints globally affecting New GCE VM network programming and Cloud Run using Direct VPC.

Details

Summary: Programming failures for New Virtual Private Cloud endpoints globally affecting New GCE VM network programming and Cloud Run using Direct VPC.
Description: We are experiencing an issue with Virtual Private Cloud (VPC) beginning on Thursday, 2024-05-16 14:44 US/Pacific.
Our engineering team continues to investigate the issue
We will provide an update by Thursday, 2024-05-16 16:57 US/Pacific with current details.
Diagnosis: Customers impacted by this issue may see slow programming in the Cloud Networking control plane. New VMs or newly migrated VMs may have delayed network programming.
For Cloud Run DirectVPC customers, Cloud Run scaling, including from 0 may not work.
Serverless VPC Connectors cannot be created or scale.
App Engine Flex deployments cannot be created or scale.
Workaround: None at this time.

May 16, 2024 23:50 UTC

DOWN

about 2 hours

Programming failures for New Virtual Private Cloud endpoints globally affecting New GCE VM network programming and Cloud Run using Direct VPC.

See more
Start Time

May 16, 2024 23:50 UTC

Type DOWN
Affected Components

Americas (regions) - Cloud Data Fusion

Europe (regions) - Cloud Data Fusion

Asia Pacific (regions) - Cloud Data Fusion

Middle East (regions) - Cloud Data Fusion

us-east5 - Cloud Data Fusion

us-south1 - Cloud Data Fusion

us-west1 - Cloud Data Fusion

us-west2 - Cloud Data Fusion

asia-east1 - Cloud Data Fusion

asia-east2 - Cloud Data Fusion

asia-northeast1 - Cloud Data Fusion

asia-northeast2 - Cloud Data Fusion

asia-northeast3 - Cloud Data Fusion

asia-south1 - Cloud Data Fusion

asia-southeast1 - Cloud Data Fusion

asia-southeast2 - Cloud Data Fusion

australia-southeast1 - Cloud Data Fusion

me-west1 - Cloud Data Fusion

europe-north1 - Cloud Data Fusion

europe-west1 - Cloud Data Fusion

europe-west2 - Cloud Data Fusion

europe-west3 - Cloud Data Fusion

us-central1 - Cloud Data Fusion

us-east1 - Cloud Data Fusion

us-east4 - Cloud Data Fusion

northamerica-northeast1 - Cloud Data Fusion

southamerica-east1 - Cloud Data Fusion

europe-west4 - Cloud Data Fusion

europe-west6 - Cloud Data Fusion

Message

Programming failures for New Virtual Private Cloud endpoints globally affecting New GCE VM network programming and Cloud Run using Direct VPC.

Details

Summary: Programming failures for New Virtual Private Cloud endpoints globally affecting New GCE VM network programming and Cloud Run using Direct VPC.
Description: We are experiencing an issue with Virtual Private Cloud (VPC) beginning on Thursday, 2024-05-16 14:44 US/Pacific.
Our engineering team continues to investigate the issue
We will provide an update by Thursday, 2024-05-16 16:57 US/Pacific with current details.
Diagnosis: Customers impacted by this issue may see slow programming in the Cloud Networking control plane. New VMs or newly migrated VMs may have delayed network programming.
For Cloud Run DirectVPC customers, Cloud Run scaling, including from 0 may not work.
Serverless VPC Connectors cannot be created or scale.
App Engine Flex deployments cannot be created or scale.
Workaround: None at this time.

November 21, 2023 10:15 UTC

WARN

less than a minute

We are experiencing an issue with AlloyDB for PostgreSQL, Backup and DR, Cloud Data Fusion, Cloud Memorystore, Google Cloud Composer, Google Cloud SQ, CreateRepository failures and high latency in us-central1 for Artifact Registry users, Environment creations fail in multiple regions due to failed Cloud SQL creations, and Cloud Resource Manager (CRM) is facing low availability on create, update and delete operations for Projects and Folders. As a result, executing these operations might result in customers encountering an ‘Unknown Error’ message.

See more
Start Time

November 21, 2023 10:15 UTC

Type WARN
Affected Components

europe-west1 - Google Cloud Composer

europe-west4 - Google Cloud SQL

europe-west6 - Google Cloud SQL

europe-west8 - Google Cloud SQL

europe-west10 - Google Cloud SQL

europe-west12 - Google Cloud SQL

northamerica-northeast2 - AlloyDB for PostgreSQL

southamerica-east1 - AlloyDB for PostgreSQL

southamerica-west1 - AlloyDB for PostgreSQL

europe-west12 - Cloud Memorystore

europe-central2 - Cloud Memorystore

europe-north1 - Cloud Memorystore

northamerica-northeast1 - Cloud Data Fusion

southamerica-east1 - Cloud Data Fusion

Asia Pacific (regions) - Cloud Data Fusion

Middle East (regions) - Cloud Data Fusion

us-west1 - Cloud Data Fusion

asia-east1 - Google Cloud SQL

europe-west9 - Google Cloud SQL

Americas (regions) - AlloyDB for PostgreSQL

Europe (regions) - AlloyDB for PostgreSQL

Asia Pacific (regions) - AlloyDB for PostgreSQL

Middle East (regions) - AlloyDB for PostgreSQL

Americas (regions) - Artifact Registry

Americas (regions) - Backup and DR

Europe (regions) - Backup and DR

Asia Pacific (regions) - Backup and DR

Americas (regions) - Cloud Data Fusion

Europe (regions) - Cloud Data Fusion

Asia Pacific (regions) - Cloud Memorystore

Middle East (regions) - Cloud Memorystore

Americas (regions) - Google Cloud SQL

Europe (regions) - Google Cloud SQL

Asia Pacific (regions) - Google Cloud SQL

Middle East (regions) - Google Cloud SQL

us-west4 - Google Cloud SQL

us-central1 - AlloyDB for PostgreSQL

us-east1 - AlloyDB for PostgreSQL

us-east4 - AlloyDB for PostgreSQL

us-east5 - AlloyDB for PostgreSQL

us-south1 - AlloyDB for PostgreSQL

us-west3 - AlloyDB for PostgreSQL

us-west4 - AlloyDB for PostgreSQL

us-central1 - Artifact Registry

us-central1 - Backup and DR

us-east1 - Backup and DR

us-east4 - Backup and DR

us-west1 - Backup and DR

us-central1 - Cloud Data Fusion

us-east1 - Cloud Data Fusion

us-east4 - Cloud Data Fusion

us-east5 - Cloud Data Fusion

us-south1 - Cloud Data Fusion

us-west2 - Cloud Data Fusion

us-central1 - Cloud Memorystore

us-east1 - Cloud Memorystore

us-east4 - Cloud Memorystore

us-east5 - Cloud Memorystore

us-south1 - Cloud Memorystore

us-west1 - Cloud Memorystore

us-west2 - Cloud Memorystore

us-west3 - Cloud Memorystore

us-west4 - Cloud Memorystore

northamerica-northeast1 - Cloud Memorystore

northamerica-northeast2 - Cloud Memorystore

southamerica-east1 - Cloud Memorystore

southamerica-west1 - Cloud Memorystore

us-east4 - Google Cloud Composer

us-west2 - Google Cloud Composer

us-west3 - Google Cloud Composer

us-west4 - Google Cloud Composer

northamerica-northeast1 - Google Cloud Composer

northamerica-northeast2 - Google Cloud Composer

southamerica-east1 - Google Cloud Composer

us-central1 - Google Cloud SQL

us-east1 - Google Cloud SQL

us-east5 - Google Cloud SQL

us-south1 - Google Cloud SQL

us-west1 - Google Cloud SQL

us-west2 - Google Cloud SQL

us-west3 - Google Cloud SQL

northamerica-northeast1 - Google Cloud SQL

northamerica-northeast2 - Google Cloud SQL

southamerica-east1 - Google Cloud SQL

southamerica-west1 - Google Cloud SQL

asia-southeast1 - Backup and DR

europe-west1 - AlloyDB for PostgreSQL

europe-west2 - AlloyDB for PostgreSQL

europe-west3 - AlloyDB for PostgreSQL

europe-west4 - AlloyDB for PostgreSQL

europe-west6 - AlloyDB for PostgreSQL

europe-west8 - AlloyDB for PostgreSQL

europe-west9 - AlloyDB for PostgreSQL

europe-west12 - AlloyDB for PostgreSQL

europe-central2 - AlloyDB for PostgreSQL

europe-north1 - AlloyDB for PostgreSQL

europe-southwest1 - AlloyDB for PostgreSQL

europe-west1 - Backup and DR

europe-west4 - Backup and DR

europe-west1 - Cloud Data Fusion

europe-west2 - Cloud Data Fusion

europe-west3 - Cloud Data Fusion

europe-west4 - Cloud Data Fusion

europe-west6 - Cloud Data Fusion

europe-north1 - Cloud Data Fusion

europe-west1 - Cloud Memorystore

europe-west4 - Cloud Memorystore

europe-west6 - Cloud Memorystore

europe-west8 - Cloud Memorystore

europe-west9 - Cloud Memorystore

europe-southwest1 - Cloud Memorystore

europe-west4 - Google Cloud Composer

europe-west6 - Google Cloud Composer

europe-west9 - Google Cloud Composer

europe-central2 - Google Cloud Composer

europe-north1 - Google Cloud Composer

europe-west1 - Google Cloud SQL

europe-west2 - Google Cloud SQL

europe-west3 - Google Cloud SQL

europe-central2 - Google Cloud SQL

europe-north1 - Google Cloud SQL

europe-southwest1 - Google Cloud SQL

asia-east1 - AlloyDB for PostgreSQL

asia-east2 - AlloyDB for PostgreSQL

asia-northeast1 - AlloyDB for PostgreSQL

asia-northeast2 - AlloyDB for PostgreSQL

asia-northeast3 - AlloyDB for PostgreSQL

asia-south1 - AlloyDB for PostgreSQL

asia-south2 - AlloyDB for PostgreSQL

asia-southeast1 - AlloyDB for PostgreSQL

asia-southeast2 - AlloyDB for PostgreSQL

australia-southeast1 - AlloyDB for PostgreSQL

australia-southeast2 - AlloyDB for PostgreSQL

asia-east1 - Backup and DR

asia-east1 - Cloud Data Fusion

asia-east2 - Cloud Data Fusion

asia-northeast1 - Cloud Data Fusion

asia-northeast2 - Cloud Data Fusion

asia-northeast3 - Cloud Data Fusion

asia-south1 - Cloud Data Fusion

asia-southeast1 - Cloud Data Fusion

asia-southeast2 - Cloud Data Fusion

australia-southeast1 - Cloud Data Fusion

Americas (regions) - Cloud Memorystore

Europe (regions) - Cloud Memorystore

asia-east1 - Cloud Memorystore

asia-east2 - Cloud Memorystore

asia-northeast1 - Cloud Memorystore

asia-northeast2 - Cloud Memorystore

asia-northeast3 - Cloud Memorystore

asia-south1 - Cloud Memorystore

asia-south2 - Cloud Memorystore

asia-southeast1 - Cloud Memorystore

asia-southeast2 - Cloud Memorystore

australia-southeast1 - Cloud Memorystore

australia-southeast2 - Cloud Memorystore

us-west1 - AlloyDB for PostgreSQL

us-west2 - AlloyDB for PostgreSQL

northamerica-northeast1 - AlloyDB for PostgreSQL

us-west4 - Backup and DR

asia-east1 - Google Cloud Composer

asia-northeast3 - Google Cloud Composer

asia-south1 - Google Cloud Composer

asia-southeast1 - Google Cloud Composer

asia-southeast2 - Google Cloud Composer

australia-southeast1 - Google Cloud Composer

australia-southeast2 - Google Cloud Composer

us-east4 - Google Cloud SQL

asia-east2 - Google Cloud SQL

asia-northeast1 - Google Cloud SQL

asia-northeast2 - Google Cloud SQL

asia-northeast3 - Google Cloud SQL

asia-south1 - Google Cloud SQL

asia-south2 - Google Cloud SQL

asia-southeast1 - Google Cloud SQL

asia-southeast2 - Google Cloud SQL

australia-southeast1 - Google Cloud SQL

australia-southeast2 - Google Cloud SQL

europe-west2 - Cloud Memorystore

europe-west3 - Cloud Memorystore

Message

We are experiencing an issue with AlloyDB for PostgreSQL, Backup and DR, Cloud Data Fusion, Cloud Memorystore, Google Cloud Composer, Google Cloud SQ, CreateRepository failures and high latency in us-central1 for Artifact Registry users, Environment creations fail in multiple regions due to failed Cloud SQL creations, and Cloud Resource Manager (CRM) is facing low availability on create, update and delete operations for Projects and Folders. As a result, executing these operations might result in customers encountering an ‘Unknown Error’ message.

Details

Summary: We are experiencing an issue with AlloyDB for PostgreSQL, Backup and DR, Cloud Data Fusion, Cloud Memorystore, Google Cloud Composer, Google Cloud SQ
Description: We are experiencing an issue with AlloyDB for PostgreSQL, Backup and DR, Cloud Data Fusion, Cloud Memorystore, Google Cloud Composer, Google Cloud SQL.
Our engineering team continues to investigate the issue.
We will provide an update by Tuesday, 2023-11-21 04:27 US/Pacific with current details.
Diagnosis: Creation of resources related to Cloud Service Networking may experience failures or delays.
Workaround: Attempt retry or await for the operation to complete.
Summary: CreateRepository failures and high latency in us-central1 for Artifact Registry users
Description: We are experiencing an issue with the Artifact Registry beginning on Monday, 2023-11-20 21:47 US/Pacific.
Our engineering team continues to investigate the issue.
We will provide an update by Tuesday, 2023-11-21 03:13 US/Pacific with current details.
Diagnosis: Customers will see on ~35% of the CreateRepository calls a deadline exceeded.
Workaround: Customers may retry the CreateRepository call until it eventually succeeds
Summary: Environment creations fail in multiple regions due to failed Cloud SQL creations
Description: We are experiencing an issue with Google Cloud Composer.
Our engineering team continues to investigate the issue.
We will provide an update by Tuesday, 2023-11-21 04:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Environment creations fail in multiple regions
Workaround: We recommend retrying if users experience this
Description:
We've received a report of an issue with Cloud Resource Manager API as of Monday, 2023-11-20 22:37 US/Pacific. We will provide more information by Tuesday, 2023-11-21 03:00 US/Pacific.
Diagnosis:
Customers impacted by this issue may find that they are unable to create/update/delete Projects or/and Folders. There is no impact on existing Projects and Folders.
Workaround:
None at this time.

November 21, 2023 10:15 UTC

WARN

about 1 hour

We are experiencing an issue with AlloyDB for PostgreSQL, Backup and DR, Cloud Data Fusion, Cloud Memorystore, Google Cloud Composer, Google Cloud SQ, CreateRepository failures and high latency in us-central1 for Artifact Registry users, Environment creations fail in multiple regions due to failed Cloud SQL creations, and Cloud Resource Manager (CRM) is facing low availability on create, update and delete operations for Projects and Folders. As a result, executing these operations might result in customers encountering an ‘Unknown Error’ message.

See more
Start Time

November 21, 2023 10:15 UTC

Type WARN
Affected Components

europe-west1 - Google Cloud Composer

europe-west4 - Google Cloud SQL

europe-west6 - Google Cloud SQL

europe-west8 - Google Cloud SQL

europe-west10 - Google Cloud SQL

europe-west12 - Google Cloud SQL

northamerica-northeast2 - AlloyDB for PostgreSQL

southamerica-east1 - AlloyDB for PostgreSQL

southamerica-west1 - AlloyDB for PostgreSQL

europe-west12 - Cloud Memorystore

europe-central2 - Cloud Memorystore

europe-north1 - Cloud Memorystore

northamerica-northeast1 - Cloud Data Fusion

southamerica-east1 - Cloud Data Fusion

Asia Pacific (regions) - Cloud Data Fusion

Middle East (regions) - Cloud Data Fusion

us-west1 - Cloud Data Fusion

asia-east1 - Google Cloud SQL

europe-west9 - Google Cloud SQL

Americas (regions) - AlloyDB for PostgreSQL

Europe (regions) - AlloyDB for PostgreSQL

Asia Pacific (regions) - AlloyDB for PostgreSQL

Middle East (regions) - AlloyDB for PostgreSQL

Americas (regions) - Artifact Registry

Americas (regions) - Backup and DR

Europe (regions) - Backup and DR

Asia Pacific (regions) - Backup and DR

Americas (regions) - Cloud Data Fusion

Europe (regions) - Cloud Data Fusion

Asia Pacific (regions) - Cloud Memorystore

Middle East (regions) - Cloud Memorystore

Americas (regions) - Google Cloud SQL

Europe (regions) - Google Cloud SQL

Asia Pacific (regions) - Google Cloud SQL

Middle East (regions) - Google Cloud SQL

us-west4 - Google Cloud SQL

us-central1 - AlloyDB for PostgreSQL

us-east1 - AlloyDB for PostgreSQL

us-east4 - AlloyDB for PostgreSQL

us-east5 - AlloyDB for PostgreSQL

us-south1 - AlloyDB for PostgreSQL

us-west3 - AlloyDB for PostgreSQL

us-west4 - AlloyDB for PostgreSQL

us-central1 - Artifact Registry

us-central1 - Backup and DR

us-east1 - Backup and DR

us-east4 - Backup and DR

us-west1 - Backup and DR

us-central1 - Cloud Data Fusion

us-east1 - Cloud Data Fusion

us-east4 - Cloud Data Fusion

us-east5 - Cloud Data Fusion

us-south1 - Cloud Data Fusion

us-west2 - Cloud Data Fusion

us-central1 - Cloud Memorystore

us-east1 - Cloud Memorystore

us-east4 - Cloud Memorystore

us-east5 - Cloud Memorystore

us-south1 - Cloud Memorystore

us-west1 - Cloud Memorystore

us-west2 - Cloud Memorystore

us-west3 - Cloud Memorystore

us-west4 - Cloud Memorystore

northamerica-northeast1 - Cloud Memorystore

northamerica-northeast2 - Cloud Memorystore

southamerica-east1 - Cloud Memorystore

southamerica-west1 - Cloud Memorystore

us-east4 - Google Cloud Composer

us-west2 - Google Cloud Composer

us-west3 - Google Cloud Composer

us-west4 - Google Cloud Composer

northamerica-northeast1 - Google Cloud Composer

northamerica-northeast2 - Google Cloud Composer

southamerica-east1 - Google Cloud Composer

us-central1 - Google Cloud SQL

us-east1 - Google Cloud SQL

us-east5 - Google Cloud SQL

us-south1 - Google Cloud SQL

us-west1 - Google Cloud SQL

us-west2 - Google Cloud SQL

us-west3 - Google Cloud SQL

northamerica-northeast1 - Google Cloud SQL

northamerica-northeast2 - Google Cloud SQL

southamerica-east1 - Google Cloud SQL

southamerica-west1 - Google Cloud SQL

asia-southeast1 - Backup and DR

europe-west1 - AlloyDB for PostgreSQL

europe-west2 - AlloyDB for PostgreSQL

europe-west3 - AlloyDB for PostgreSQL

europe-west4 - AlloyDB for PostgreSQL

europe-west6 - AlloyDB for PostgreSQL

europe-west8 - AlloyDB for PostgreSQL

europe-west9 - AlloyDB for PostgreSQL

europe-west12 - AlloyDB for PostgreSQL

europe-central2 - AlloyDB for PostgreSQL

europe-north1 - AlloyDB for PostgreSQL

europe-southwest1 - AlloyDB for PostgreSQL

europe-west1 - Backup and DR

europe-west4 - Backup and DR

europe-west1 - Cloud Data Fusion

europe-west2 - Cloud Data Fusion

europe-west3 - Cloud Data Fusion

europe-west4 - Cloud Data Fusion

europe-west6 - Cloud Data Fusion

europe-north1 - Cloud Data Fusion

europe-west1 - Cloud Memorystore

europe-west4 - Cloud Memorystore

europe-west6 - Cloud Memorystore

europe-west8 - Cloud Memorystore

europe-west9 - Cloud Memorystore

europe-southwest1 - Cloud Memorystore

europe-west4 - Google Cloud Composer

europe-west6 - Google Cloud Composer

europe-west9 - Google Cloud Composer

europe-central2 - Google Cloud Composer

europe-north1 - Google Cloud Composer

europe-west1 - Google Cloud SQL

europe-west2 - Google Cloud SQL

europe-west3 - Google Cloud SQL

europe-central2 - Google Cloud SQL

europe-north1 - Google Cloud SQL

europe-southwest1 - Google Cloud SQL

asia-east1 - AlloyDB for PostgreSQL

asia-east2 - AlloyDB for PostgreSQL

asia-northeast1 - AlloyDB for PostgreSQL

asia-northeast2 - AlloyDB for PostgreSQL

asia-northeast3 - AlloyDB for PostgreSQL

asia-south1 - AlloyDB for PostgreSQL

asia-south2 - AlloyDB for PostgreSQL

asia-southeast1 - AlloyDB for PostgreSQL

asia-southeast2 - AlloyDB for PostgreSQL

australia-southeast1 - AlloyDB for PostgreSQL

australia-southeast2 - AlloyDB for PostgreSQL

asia-east1 - Backup and DR

asia-east1 - Cloud Data Fusion

asia-east2 - Cloud Data Fusion

asia-northeast1 - Cloud Data Fusion

asia-northeast2 - Cloud Data Fusion

asia-northeast3 - Cloud Data Fusion

asia-south1 - Cloud Data Fusion

asia-southeast1 - Cloud Data Fusion

asia-southeast2 - Cloud Data Fusion

australia-southeast1 - Cloud Data Fusion

Americas (regions) - Cloud Memorystore

Europe (regions) - Cloud Memorystore

asia-east1 - Cloud Memorystore

asia-east2 - Cloud Memorystore

asia-northeast1 - Cloud Memorystore

asia-northeast2 - Cloud Memorystore

asia-northeast3 - Cloud Memorystore

asia-south1 - Cloud Memorystore

asia-south2 - Cloud Memorystore

asia-southeast1 - Cloud Memorystore

asia-southeast2 - Cloud Memorystore

australia-southeast1 - Cloud Memorystore

australia-southeast2 - Cloud Memorystore

us-west1 - AlloyDB for PostgreSQL

us-west2 - AlloyDB for PostgreSQL

northamerica-northeast1 - AlloyDB for PostgreSQL

us-west4 - Backup and DR

asia-east1 - Google Cloud Composer

asia-northeast3 - Google Cloud Composer

asia-south1 - Google Cloud Composer

asia-southeast1 - Google Cloud Composer

asia-southeast2 - Google Cloud Composer

australia-southeast1 - Google Cloud Composer

australia-southeast2 - Google Cloud Composer

us-east4 - Google Cloud SQL

asia-east2 - Google Cloud SQL

asia-northeast1 - Google Cloud SQL

asia-northeast2 - Google Cloud SQL

asia-northeast3 - Google Cloud SQL

asia-south1 - Google Cloud SQL

asia-south2 - Google Cloud SQL

asia-southeast1 - Google Cloud SQL

asia-southeast2 - Google Cloud SQL

australia-southeast1 - Google Cloud SQL

australia-southeast2 - Google Cloud SQL

europe-west2 - Cloud Memorystore

europe-west3 - Cloud Memorystore

Message

We are experiencing an issue with AlloyDB for PostgreSQL, Backup and DR, Cloud Data Fusion, Cloud Memorystore, Google Cloud Composer, Google Cloud SQ, CreateRepository failures and high latency in us-central1 for Artifact Registry users, Environment creations fail in multiple regions due to failed Cloud SQL creations, and Cloud Resource Manager (CRM) is facing low availability on create, update and delete operations for Projects and Folders. As a result, executing these operations might result in customers encountering an ‘Unknown Error’ message.

Details

Summary: We are experiencing an issue with AlloyDB for PostgreSQL, Backup and DR, Cloud Data Fusion, Cloud Memorystore, Google Cloud Composer, Google Cloud SQ
Description: We are experiencing an issue with AlloyDB for PostgreSQL, Backup and DR, Cloud Data Fusion, Cloud Memorystore, Google Cloud Composer, Google Cloud SQL.
Our engineering team continues to investigate the issue.
We will provide an update by Tuesday, 2023-11-21 04:27 US/Pacific with current details.
Diagnosis: Creation of resources related to Cloud Service Networking may experience failures or delays.
Workaround: Attempt retry or await for the operation to complete.
Summary: CreateRepository failures and high latency in us-central1 for Artifact Registry users
Description: We are experiencing an issue with the Artifact Registry beginning on Monday, 2023-11-20 21:47 US/Pacific.
Our engineering team continues to investigate the issue.
We will provide an update by Tuesday, 2023-11-21 03:13 US/Pacific with current details.
Diagnosis: Customers will see on ~35% of the CreateRepository calls a deadline exceeded.
Workaround: Customers may retry the CreateRepository call until it eventually succeeds
Summary: Environment creations fail in multiple regions due to failed Cloud SQL creations
Description: We are experiencing an issue with Google Cloud Composer.
Our engineering team continues to investigate the issue.
We will provide an update by Tuesday, 2023-11-21 04:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Environment creations fail in multiple regions
Workaround: We recommend retrying if users experience this
Description:
We've received a report of an issue with Cloud Resource Manager API as of Monday, 2023-11-20 22:37 US/Pacific. We will provide more information by Tuesday, 2023-11-21 03:00 US/Pacific.
Diagnosis:
Customers impacted by this issue may find that they are unable to create/update/delete Projects or/and Folders. There is no impact on existing Projects and Folders.
Workaround:
None at this time.

October 05, 2023 18:30 UTC

WARN

less than a minute

We are investigating an issue with some ‘Cloud Memorystore for Redis’ instances that fail health checks and are not being repaired correctly, leaving them in an unavailable state. and Global: Google Kubernetes Engine Nodepool Upgrade Failures

See more
Start Time

October 05, 2023 18:30 UTC

Type WARN
Affected Components

Americas (regions) - Cloud Data Fusion

us-central1 - Batch

Americas (regions) - Google Cloud Dataflow

Americas (regions) - Google Cloud Dataproc

Americas (regions) - Batch

Americas (regions) - Cloud Filestore

Americas (regions) - Google Cloud Networking

Americas (regions) - Google Compute Engine

Americas (regions) - Virtual Private Cloud (VPC)

us-central1 - Cloud Data Fusion

us-central1 - Cloud Filestore

us-central1 - Google Cloud Dataflow

us-central1 - Google Cloud Dataproc

us-central1 - Google Cloud Networking

us-central1 - Google Cloud SQL

us-central1 - Google Compute Engine

us-central1 - Google Kubernetes Engine

us-central1 - Virtual Private Cloud (VPC)

Americas (regions) - Google Cloud SQL

Message

We are investigating an issue with some ‘Cloud Memorystore for Redis’ instances that fail health checks and are not being repaired correctly, leaving them in an unavailable state. and Global: Google Kubernetes Engine Nodepool Upgrade Failures

Details

Summary: We are investigating an issue with some ‘Cloud Memorystore for Redis’ instances that fail health checks and are not being repaired correctly, leaving them in an unavailable state.
Description: A fix rollout is currently underway and our engineering team will continue to mitigate the unhealthy nodes as they appear until the fix is rolled out.
We expect the fix roll out to complete by Monday, 2023-10-09
We will provide more information by Monday, 2023-10-09 14:00 US/Pacific.
Diagnosis: Impacted ‘Memorystore for Redis’ customers may observe unresponsive nodes.
Please note that ‘Memorystore for Memcached’ and ‘Memorystore for Redis Cluster’ are not impacted by this issue
Workaround: None at this time.
Summary: Global: Google Kubernetes Engine Nodepool Upgrade Failures
Description: Our engineering team is working on a mitigation which will rollout over the next few days. We will provide an update by Friday, 2023-10-06 12:00 US/Pacific with current details.
Diagnosis: A small number of customers are experiencing failed nodepool upgrades. Customers experiencing this, may see "Internal error" in Google Cloud Console. Retrying is suggested but may not always work.
Workaround: Customers can re-create nodepools at the new version instead of upgrading in-place.

2024-05-17 17:47:08 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-17 17:47:08 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-17 17:47:08 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-17 17:47:08 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-17 17:47:08 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Cloud Data Fusion History

StatusGator has over 7 years of Cloud Data Fusion status history.

2 status changes in the last 24 hours

Cloud Data Fusion status, last 24 hours:

6:00 PM
12:00 AM
6:00 AM
12:00 PM
6:00 PM
6:00 PM
6:00 AM
6:00 PM
  • Up: 22 hours

  • Warn: 0 minutes

  • Down: 2 hours

Cloud Data Fusion Outage and Status History

We've been monitoring Cloud Data Fusion outages since August 22, 2016.
Here's the history of service outages we've observed from the Cloud Data Fusion Status Page:

April 2024

March 2024

  • Up

  • Warn

  • Down

Instant enriched data from
3,600 status pages

About Our Cloud Data Fusion Status Page Integration

Cloud Data Fusion is a Cloud Infrastructure solution that StatusGator has been monitoring since August 2016. Over the past almost 8 years, we have collected data on on more than 2,255 outages that affected Cloud Data Fusion users. When Cloud Data Fusion publishes downtime on their status page, they do so across 6,377 components and 66 groups using 3 different statuses: up, warn, and down which we use to provide granular uptime metrics and notifications.

More than 2,100 StatusGator users monitor Cloud Data Fusion to get notified when it's down or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 408,000 notifications to our users about Cloud Data Fusion incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Cloud Data Fusion is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Cloud Data Fusion is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Cloud Data Fusion does not post separate notifications for planned maintenance work so we are unable to send notifications when maintenance windows begin. If you need Cloud Data Fusion maintenance notifications, please email us.

Cloud Data Fusion does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Cloud Data Fusion maintenance events into your unified calendar.

When Cloud Data Fusion posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Cloud Data Fusion has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Cloud Data Fusion has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Cloud Data Fusion Down?

Are you experiencing issues with Cloud Data Fusion? Sign up to receive notifications when Cloud Data Fusion publishes outages.

Cloud Data Fusion Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,600 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Cloud Data Fusion?

Sign up for StatusGator and see all historical information about Cloud Data Fusion outages and performance issues. Get free, instant notifications when Cloud Data Fusion goes down.