Is Google Cloud AlloyDB for PostgreSQL down?
Current Google Cloud AlloyDB for PostgreSQL status is UP

We checked the official Google Cloud AlloyDB for PostgreSQL Status Page 2 min. 9 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 AlloyDB for PostgreSQL Outages and Issues

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

Start Time

Type

Length

Message

Details

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.

November 01, 2023 19:05 UTC

WARN

about 9 hours

We are experiencing an issue with AlloyDB for PostgresSQL in us-central1

See more
Start Time

November 01, 2023 19:05 UTC

Type WARN
Affected Components

Americas (regions) - AlloyDB for PostgreSQL

Message

We are experiencing an issue with AlloyDB for PostgresSQL in us-central1

Details

Summary: We are experiencing an issue with AlloyDB for PostgresSQL in us-central1
Description: We are experiencing an intermittent issue with AlloyDB for PostgreSQL.
Our engineering team continues to investigate the issue.
We will provide an update by Wednesday, 2023-11-01 13:20 US/Pacific with current details.
Diagnosis: "Some customers in us-central1 may experience intermittent errors when attempting to create new instances for AlloyDB and some customers may additionally experience potential flag update failures."
Workaround: None at this time.

November 01, 2023 19:00 UTC

WARN

5 minutes

We are experiencing an issue with AlloyDB

See more
Start Time

November 01, 2023 19:00 UTC

Type WARN
Affected Components

us-central1 - AlloyDB for PostgreSQL

Message

We are experiencing an issue with AlloyDB

Details

Summary: We are experiencing an issue with AlloyDB
Description: We are experiencing an issue with AlloyDB for PostgreSQL.
Our engineering team continues to investigate the issue.
We will provide an update by Wednesday, 2023-11-01 13:00 US/Pacific with current details.
Diagnosis: "Some customers may experience intermittent errors when attempting to create new instances for AlloyDB and some customers may additionally experience potential flag update failures."
Workaround: None at this time.

June 28, 2023 00:25 UTC

WARN

less than a minute

Global: A small number of customers unable to initialize Backup and DR if their projects are not attached to an organization.

See more
Start Time

June 28, 2023 00:25 UTC

Type WARN
Affected Components

us-east1 - Backup and DR

europe-west1 - Backup and DR

Americas (regions) - AlloyDB for PostgreSQL

Americas (regions) - Backup and DR

Europe (regions) - Backup and DR

Asia Pacific (regions) - Backup and DR

us-east1 - AlloyDB for PostgreSQL

us-central1 - Backup and DR

us-east4 - Backup and DR

us-west1 - Backup and DR

us-west4 - Backup and DR

europe-west4 - Backup and DR

asia-east1 - Backup and DR

asia-southeast1 - Backup and DR

Message

Global: A small number of customers unable to initialize Backup and DR if their projects are not attached to an organization.

Details

Summary: Global: A small number of customers unable to initialize Backup and DR if their projects are not attached to an organization.
Description: We've received a report of an issue with Backup and DR as of Tuesday, 2023-06-27 16:59 US/Pacific.
We will provide more information by Thursday, 2023-06-29 13:30 US/Pacific.
Diagnosis: Affected customers not able to initialize Backup and DR if their projects are not attached to an organization.
Workaround: None at this time.

2024-04-11 16:06:21 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-11 16:06:21 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-11 16:06:21 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-11 16:06:21 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-11 16:06:21 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Google Cloud AlloyDB for PostgreSQL History

StatusGator has over 7 years of Google Cloud AlloyDB for PostgreSQL status history.

No outages or status changes in the last 24 hours

Google Cloud AlloyDB for PostgreSQL status, last 24 hours:

5:00 PM
11:00 PM
5:00 AM
11:00 AM
5:00 PM
5:00 PM
5:00 AM
5:00 PM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

Google Cloud AlloyDB for PostgreSQL Outage and Status History

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

April 2024

March 2024

February 2024

  • Up

  • Warn

  • Down

Instant enriched data from
3,580 status pages

About Our Google Cloud AlloyDB for PostgreSQL Status Page Integration

Google Cloud AlloyDB for PostgreSQL is a Cloud Infrastructure solution that StatusGator has been monitoring since August 2016. Over the past over 7 years, we have collected data on on more than 2,213 outages that affected Google Cloud AlloyDB for PostgreSQL users. When Google Cloud AlloyDB for PostgreSQL publishes downtime on their status page, they do so across 6,262 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 AlloyDB for PostgreSQL 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 402,700 notifications to our users about Google Cloud AlloyDB for PostgreSQL incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Google Cloud AlloyDB for PostgreSQL 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 AlloyDB for PostgreSQL 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 AlloyDB for PostgreSQL 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 AlloyDB for PostgreSQL maintenance notifications, please email us.

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

When Google Cloud AlloyDB for PostgreSQL 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 AlloyDB for PostgreSQL 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 AlloyDB for PostgreSQL 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 AlloyDB for PostgreSQL Down?

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

Google Cloud AlloyDB for PostgreSQL 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,580 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 AlloyDB for PostgreSQL?

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