Is Google Cloud SQL down?
Current Google Cloud SQL status is UP

We checked the official Google Cloud SQL Status Page 48 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 Google Cloud SQL Outages and Issues

Follow the recent outages and downtime for Google Cloud SQL in the table below.

Start Time

Type

Length

Message

Details

May 17, 2024 01:40 UTC

DOWN

less than a minute

Multiple cloud products are experiencing network connectivity issues. New instances of several cloud products will come up without a network in many regions.

See more
Start Time

May 17, 2024 01:40 UTC

Type DOWN
Affected Components

asia-east1 - Batch

asia-east2 - Batch

asia-northeast1 - Batch

asia-southeast2 - Batch

australia-southeast1 - Batch

australia-southeast2 - Batch

us-central1 - Batch

us-east5 - Batch

Asia Pacific (regions) - Batch

europe-west12 - 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) - Google Cloud SQL

Europe (regions) - Google Cloud SQL

Asia Pacific (regions) - Google Cloud SQL

Middle East (regions) - Google Cloud SQL

Africa (regions) - 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-west1 - AlloyDB for PostgreSQL

us-west2 - AlloyDB for PostgreSQL

us-west3 - AlloyDB for PostgreSQL

southamerica-west1 - AlloyDB for PostgreSQL

us-south1 - Batch

us-west1 - Batch

us-west2 - Batch

us-west3 - Batch

us-west4 - Batch

northamerica-northeast1 - Batch

northamerica-northeast2 - Batch

southamerica-east1 - Batch

Americas (regions) - Batch

us-central1 - Google Cloud SQL

us-east1 - Google Cloud SQL

us-east4 - 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

us-west4 - Google Cloud SQL

northamerica-northeast1 - Google Cloud SQL

northamerica-northeast2 - Google Cloud SQL

southamerica-west1 - Google Cloud SQL

europe-west2 - AlloyDB for PostgreSQL

europe-west3 - AlloyDB for PostgreSQL

europe-west4 - AlloyDB for PostgreSQL

europe-west8 - AlloyDB for PostgreSQL

europe-west9 - AlloyDB for PostgreSQL

europe-north1 - AlloyDB for PostgreSQL

europe-southwest1 - AlloyDB for PostgreSQL

Europe (regions) - Batch

europe-west1 - Batch

europe-west2 - Batch

europe-west3 - Batch

europe-west10 - Batch

europe-west1 - Google Cloud SQL

europe-west2 - Google Cloud SQL

europe-west3 - Google Cloud SQL

europe-west4 - Google Cloud SQL

europe-west6 - Google Cloud SQL

europe-west8 - Google Cloud SQL

europe-west9 - Google Cloud SQL

europe-west10 - Google Cloud SQL

europe-central2 - 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 - Google Cloud SQL

asia-south2 - Google Cloud SQL

asia-southeast2 - Google Cloud SQL

australia-southeast1 - Google Cloud SQL

australia-southeast2 - Google Cloud SQL

me-central1 - AlloyDB for PostgreSQL

me-west1 - AlloyDB for PostgreSQL

me-central2 - Batch

me-west1 - Batch

me-central1 - Google Cloud SQL

me-central2 - Google Cloud SQL

africa-south1 - Google Cloud SQL

europe-north1 - Google Cloud SQL

Middle East (regions) - Batch

europe-west6 - AlloyDB for PostgreSQL

asia-northeast3 - Batch

asia-south2 - Batch

me-west1 - Google Cloud SQL

us-east1 - Batch

europe-west4 - Batch

europe-west8 - Batch

europe-west9 - Batch

us-east4 - Batch

asia-south1 - Batch

asia-southeast1 - Google Cloud SQL

europe-west12 - Batch

europe-central2 - Batch

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

southamerica-east1 - Google Cloud SQL

southamerica-west1 - Batch

us-west4 - AlloyDB for PostgreSQL

northamerica-northeast1 - AlloyDB for PostgreSQL

northamerica-northeast2 - AlloyDB for PostgreSQL

southamerica-east1 - AlloyDB for PostgreSQL

europe-west1 - AlloyDB for PostgreSQL

europe-west10 - AlloyDB for PostgreSQL

europe-west12 - AlloyDB for PostgreSQL

europe-central2 - AlloyDB for PostgreSQL

europe-north1 - Batch

europe-southwest1 - Batch

me-central1 - Batch

europe-west6 - Batch

asia-southeast1 - Batch

asia-northeast2 - Batch

Message

Multiple cloud products are experiencing network connectivity issues. New instances of several cloud products will come up without a network in many regions.

Details

Summary: Multiple cloud products are experiencing network connectivity issues. New instances of several cloud products will come up without a network in many regions.
Description: We are seeing recovery for most of the affected products across all regions.
Cloud Functions, Cloud Run, and App Engine Flex are recovered as of 18:06 US/Pacific
Google engineers are actively working to fully restore control plane functionality for all affected products and regions.
We do not have an ETA for complete mitigation at this point
We will provide an update by Thursday, 2024-05-16 18:55 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.
- New connections via Google Cloud Load Balancer may also fail to establish.
- For GKE cluster creation and deletion, node pool creation and deletion, scale ups, upgrades, as well as changes to networking configuration are impacted.
- For Cloud Run DirectVPC customers, Cloud Run scaling, including from 0 will 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 17, 2024 01:40 UTC

DOWN

5 minutes

Multiple cloud products are experiencing network connectivity issues. New instances of several cloud products will come up without a network in many regions.

See more
Start Time

May 17, 2024 01:40 UTC

Type DOWN
Affected Components

asia-east1 - Batch

asia-east2 - Batch

asia-northeast1 - Batch

asia-southeast2 - Batch

australia-southeast1 - Batch

australia-southeast2 - Batch

us-central1 - Batch

us-east5 - Batch

Asia Pacific (regions) - Batch

europe-west12 - 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) - Google Cloud SQL

Europe (regions) - Google Cloud SQL

Asia Pacific (regions) - Google Cloud SQL

Middle East (regions) - Google Cloud SQL

Africa (regions) - 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-west1 - AlloyDB for PostgreSQL

us-west2 - AlloyDB for PostgreSQL

us-west3 - AlloyDB for PostgreSQL

southamerica-west1 - AlloyDB for PostgreSQL

us-south1 - Batch

us-west1 - Batch

us-west2 - Batch

us-west3 - Batch

us-west4 - Batch

northamerica-northeast1 - Batch

northamerica-northeast2 - Batch

southamerica-east1 - Batch

Americas (regions) - Batch

us-central1 - Google Cloud SQL

us-east1 - Google Cloud SQL

us-east4 - 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

us-west4 - Google Cloud SQL

northamerica-northeast1 - Google Cloud SQL

northamerica-northeast2 - Google Cloud SQL

southamerica-west1 - Google Cloud SQL

europe-west2 - AlloyDB for PostgreSQL

europe-west3 - AlloyDB for PostgreSQL

europe-west4 - AlloyDB for PostgreSQL

europe-west8 - AlloyDB for PostgreSQL

europe-west9 - AlloyDB for PostgreSQL

europe-north1 - AlloyDB for PostgreSQL

europe-southwest1 - AlloyDB for PostgreSQL

Europe (regions) - Batch

europe-west1 - Batch

europe-west2 - Batch

europe-west3 - Batch

europe-west10 - Batch

europe-west1 - Google Cloud SQL

europe-west2 - Google Cloud SQL

europe-west3 - Google Cloud SQL

europe-west4 - Google Cloud SQL

europe-west6 - Google Cloud SQL

europe-west8 - Google Cloud SQL

europe-west9 - Google Cloud SQL

europe-west10 - Google Cloud SQL

europe-central2 - 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 - Google Cloud SQL

asia-south2 - Google Cloud SQL

asia-southeast2 - Google Cloud SQL

australia-southeast1 - Google Cloud SQL

australia-southeast2 - Google Cloud SQL

me-central1 - AlloyDB for PostgreSQL

me-west1 - AlloyDB for PostgreSQL

me-central2 - Batch

me-west1 - Batch

me-central1 - Google Cloud SQL

me-central2 - Google Cloud SQL

africa-south1 - Google Cloud SQL

europe-north1 - Google Cloud SQL

Middle East (regions) - Batch

europe-west6 - AlloyDB for PostgreSQL

asia-northeast3 - Batch

asia-south2 - Batch

me-west1 - Google Cloud SQL

us-east1 - Batch

europe-west4 - Batch

europe-west8 - Batch

europe-west9 - Batch

us-east4 - Batch

asia-south1 - Batch

asia-southeast1 - Google Cloud SQL

europe-west12 - Batch

europe-central2 - Batch

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

southamerica-east1 - Google Cloud SQL

southamerica-west1 - Batch

us-west4 - AlloyDB for PostgreSQL

northamerica-northeast1 - AlloyDB for PostgreSQL

northamerica-northeast2 - AlloyDB for PostgreSQL

southamerica-east1 - AlloyDB for PostgreSQL

europe-west1 - AlloyDB for PostgreSQL

europe-west10 - AlloyDB for PostgreSQL

europe-west12 - AlloyDB for PostgreSQL

europe-central2 - AlloyDB for PostgreSQL

europe-north1 - Batch

europe-southwest1 - Batch

me-central1 - Batch

europe-west6 - Batch

asia-southeast1 - Batch

asia-northeast2 - Batch

Message

Multiple cloud products are experiencing network connectivity issues. New instances of several cloud products will come up without a network in many regions.

Details

Summary: Multiple cloud products are experiencing network connectivity issues. New instances of several cloud products will come up without a network in many regions.
Description: We are seeing recovery for most of the affected products across all regions.
Cloud Functions, Cloud Run, and App Engine Flex are recovered as of 18:06 US/Pacific
Google engineers are actively working to fully restore control plane functionality for all affected products and regions.
We do not have an ETA for complete mitigation at this point
We will provide an update by Thursday, 2024-05-16 18:55 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.
- New connections via Google Cloud Load Balancer may also fail to establish.
- For GKE cluster creation and deletion, node pool creation and deletion, scale ups, upgrades, as well as changes to networking configuration are impacted.
- For Cloud Run DirectVPC customers, Cloud Run scaling, including from 0 will 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 09, 2024 05:30 UTC

WARN

less than a minute

Apigee API Platform - Service Issues

See more
Start Time

May 09, 2024 05:30 UTC

Type WARN
Affected Components

Asia Pacific (regions) - Cloud Filestore

Asia Pacific (regions) - Google BigQuery

Asia Pacific (regions) - Google Cloud Bigtable

Asia Pacific (regions) - Google Cloud Dataflow

Asia Pacific (regions) - Google Cloud Pub/Sub

Asia Pacific (regions) - Google Compute Engine

Asia Pacific (regions) - Persistent Disk

Asia Pacific (regions) - Virtual Private Cloud (VPC)

australia-southeast1 - Cloud Filestore

australia-southeast1 - Google Cloud Bigtable

australia-southeast1 - Google Cloud Dataflow

australia-southeast1 - Google Cloud Pub/Sub

australia-southeast1 - Google Cloud SQL

australia-southeast1 - Google Compute Engine

australia-southeast1 - Persistent Disk

australia-southeast1 - Virtual Private Cloud (VPC)

australia-southeast1 - Apigee

australia-southeast1 - Google BigQuery

Asia Pacific (regions) - Cloud Logging

australia-southeast1 - Cloud Logging

Asia Pacific (regions) - Google Cloud SQL

Message

Apigee API Platform - Service Issues

Details

Summary: Apigee API Platform - Service Issues
Description: Starting Wednesday, 2024-05-08 16:41 US/Pacific, customers making use of caching policies in their API proxies are experiencing issues with Apigee API Platform services.
The mitigation roll out is progressing region by region, and the roll out will continue till all regions have received the update. We expect this to be completed within the next 8 hours. We do not have an ETA for completion of mitigation at this time.
We will provide an update by Thursday, 2024-05-09 08:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Impacted customers may experience latency in the completion of their API calls.
Workaround: There is no workaround at this time.

May 09, 2024 05:30 UTC

WARN

8 days

Apigee API Platform - Service Issues

See more
Start Time

May 09, 2024 05:30 UTC

Type WARN
Affected Components

Asia Pacific (regions) - Cloud Filestore

Asia Pacific (regions) - Google BigQuery

Asia Pacific (regions) - Google Cloud Bigtable

Asia Pacific (regions) - Google Cloud Dataflow

Asia Pacific (regions) - Google Cloud Pub/Sub

Asia Pacific (regions) - Google Compute Engine

Asia Pacific (regions) - Persistent Disk

Asia Pacific (regions) - Virtual Private Cloud (VPC)

australia-southeast1 - Cloud Filestore

australia-southeast1 - Google Cloud Bigtable

australia-southeast1 - Google Cloud Dataflow

australia-southeast1 - Google Cloud Pub/Sub

australia-southeast1 - Google Cloud SQL

australia-southeast1 - Google Compute Engine

australia-southeast1 - Persistent Disk

australia-southeast1 - Virtual Private Cloud (VPC)

australia-southeast1 - Apigee

australia-southeast1 - Google BigQuery

Asia Pacific (regions) - Cloud Logging

australia-southeast1 - Cloud Logging

Asia Pacific (regions) - Google Cloud SQL

Message

Apigee API Platform - Service Issues

Details

Summary: Apigee API Platform - Service Issues
Description: Starting Wednesday, 2024-05-08 16:41 US/Pacific, customers making use of caching policies in their API proxies are experiencing issues with Apigee API Platform services.
The mitigation roll out is progressing region by region, and the roll out will continue till all regions have received the update. We expect this to be completed within the next 8 hours. We do not have an ETA for completion of mitigation at this time.
We will provide an update by Thursday, 2024-05-09 08:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Impacted customers may experience latency in the completion of their API calls.
Workaround: There is no workaround at this time.

May 09, 2024 04:10 UTC

DOWN

less than a minute

Multiple services impacted in australia-southeast1. and Apigee API Platform - Service Issues

See more
Start Time

May 09, 2024 04:10 UTC

Type DOWN
Affected Components

australia-southeast1 - Google Cloud SQL

Asia Pacific (regions) - Google Cloud SQL

Message

Multiple services impacted in australia-southeast1. and Apigee API Platform - Service Issues

Details

Summary: Multiple services impacted in australia-southeast1.
Description: We are experiencing an issue with Big Query, Google filestore, Cloud PubSub beginning at Wednesday, 2024-05-08 18:45 US/Pacific.
Mitigation strategy has been identified. The services are now recovering.
We will provide an update by Wednesday, 2024-05-08 21:30 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Multiple GCP services are experiencing issues in australia-southeast1 region.
**Persistent Disk:** While most devices have restored their functionality, some users might encounter slow or unavailable devices.
**Google Cloud Dataflow:** Users experienced issues for streaming jobs with Watermark increasing. The issue with Google Cloud Dataflow is mitigated at 2024-05-08 19:47:27 PDT.
**Google Cloud Pub/Sub:** The PubSub impact is mitigated.
**Google BigQuery:** The impacted users may experience failures with the bigquery jobs in the australia-southeast1 Region.
**Google Compute Engine:** VM’s went into repair for around 45 minutes and have started recovering. The issue with the Compute Engine is mitigated at 2024-05-08 19:43:43 PDT.
**Cloud Filestore:** The impacted customers are unable to access the NFS Filestores in the australia-southeast1-a Zone.
Workaround: None at this time.
Summary: Apigee API Platform - Service Issues
Description: Starting Wednesday, 2024-05-08 16:41 US/Pacific, customers making use of caching policies in their API proxies are experiencing issues with Apigee API Platform services.
The mitigation roll out is in progress, we do not have an ETA for completion of mitigation at this time.
We will provide an update by Wednesday, 2024-05-08 23:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Impacted customers may experience latency in the completion of their API calls.
Workaround: There is no workaround at this time.

2024-05-17 17:04:38 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-17 17:04:38 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-17 17:04:38 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-17 17:04:38 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-17 17:04:38 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Google Cloud SQL History

StatusGator has over 7 years of Google Cloud SQL status history.

2 status changes in the last 24 hours

Google Cloud SQL 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: 24 hours

  • Warn: 0 minutes

  • Down: 5 minutes

Google Cloud SQL Outage and Status History

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

Instant enriched data from
3,600 status pages

About Our Google Cloud SQL Status Page Integration

Google Cloud SQL 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 Google Cloud SQL users. When Google Cloud SQL 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 Google Cloud SQL 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 Google Cloud SQL incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Google Cloud SQL 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 Google Cloud SQL 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.

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

Google Cloud SQL 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 Google Cloud SQL maintenance events into your unified calendar.

When Google Cloud SQL 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 Google Cloud SQL 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 Google Cloud SQL 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!

Google Cloud SQL Down?

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

Google Cloud SQL 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 Google Cloud SQL?

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