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

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

Follow the recent outages and downtime for Google Cloud Batch 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.

April 22, 2024 21:15 UTC

DOWN

less than a minute

Google Batch - Service Issues - uscentral1

See more
Start Time

April 22, 2024 21:15 UTC

Type DOWN
Affected Components

us-central1 - Batch

Americas (regions) - Batch

Message

Google Batch - Service Issues - uscentral1

Details

Summary: Google Batch - Service Issues - uscentral1
Description: We've received a report of an issue with Batch as of Monday, 2024-04-22 09:00 US/Pacific.
This issue is impacting all new incoming requests for batch jobs in us-central1.
Our engineering team is investigating the issue in hand to ascertain a mitigation plan.
We will provide more information by Monday, 2024-04-22 15:15 US/Pacific
Diagnosis: Customers trying to use Batch would experience delays while changing the status of their batch jobs from Queued to Scheduled.
Workaround: Customers could try submitting their jobs from another region as a workaround.

April 22, 2024 21:15 UTC

DOWN

about 8 hours

Google Batch - Service Issues - uscentral1

See more
Start Time

April 22, 2024 21:15 UTC

Type DOWN
Affected Components

us-central1 - Batch

Americas (regions) - Batch

Message

Google Batch - Service Issues - uscentral1

Details

Summary: Google Batch - Service Issues - uscentral1
Description: We've received a report of an issue with Batch as of Monday, 2024-04-22 09:00 US/Pacific.
This issue is impacting all new incoming requests for batch jobs in us-central1.
Our engineering team is investigating the issue in hand to ascertain a mitigation plan.
We will provide more information by Monday, 2024-04-22 15:15 US/Pacific
Diagnosis: Customers trying to use Batch would experience delays while changing the status of their batch jobs from Queued to Scheduled.
Workaround: Customers could try submitting their jobs from another region as a workaround.

March 12, 2024 23:35 UTC

WARN

less than a minute

Customers may experience elevated latencies in Apigee Sense.

See more
Start Time

March 12, 2024 23:35 UTC

Type WARN
Affected Components

us-south1 - Batch

us-central1 - Batch

us-east1 - Batch

us-east5 - Batch

us-west1 - Batch

us-west2 - Batch

us-west3 - Batch

us-west4 - Batch

us-east4 - Batch

northamerica-northeast1 - Batch

northamerica-northeast2 - Batch

southamerica-east1 - Batch

southamerica-west1 - Batch

Message

Customers may experience elevated latencies in Apigee Sense.

Details

Summary: Customers may experience elevated latencies in Apigee Sense.
Description: Mitigation work is still underway by our engineering team.
We do not have an ETA for mitigation at this point.
We will provide more information by Tuesday, 2024-03-12 17:00 US/Pacific.
Diagnosis: Impacted customers may experience delays in bot detection which may in turn affect blocking rules
Apigee Sense Protection feature is working as intended.
Workaround: None at this time.

2024-05-20 09:57:03 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-20 09:57:03 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-20 09:57:03 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-20 09:57:03 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-05-20 09:57:03 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Google Cloud Batch History

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

No outages or status changes in the last 24 hours

Google Cloud Batch status, last 24 hours:

10:00 AM
4:00 PM
10:00 PM
4:00 AM
10:00 AM
10:00 AM
10:00 PM
10:00 AM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

Google Cloud Batch Outage and Status History

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

Instant enriched data from
3,600 status pages

About Our Google Cloud Batch Status Page Integration

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

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

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

When Google Cloud Batch 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 Batch 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 Batch 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 Batch Down?

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

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

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