Service Health

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

Incident affecting Cloud Run

Global : Cloud Run is experiencing elevated latency and deployment failures

Incident began at 2023-04-01 16:40 and ended at 2023-04-01 19:25 (all times are US/Pacific).

Previously affected location(s)

Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Osaka (asia-northeast2)Seoul (asia-northeast3)Mumbai (asia-south1)Delhi (asia-south2)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Melbourne (australia-southeast2)Warsaw (europe-central2)Finland (europe-north1)Madrid (europe-southwest1)Belgium (europe-west1)Turin (europe-west12)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)Milan (europe-west8)Paris (europe-west9)Tel Aviv (me-west1)Montréal (northamerica-northeast1)Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Santiago (southamerica-west1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Columbus (us-east5)Dallas (us-south1)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)

Date Time Description
3 Apr 2023 11:30 PDT

Mini Incident Report

We apologize for the inconvenience this service disruption/outage may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support.

(All Times US/Pacific)

Incident Start: 1 April 2023 16:40

Incident End: 1 April 2023 19:25

Duration: 2 hours, 45 minutes

Affected Services and Features:

Cloud Run - Deployments

Regions/Zones: Global

Description:

Cloud Run experienced elevated latency and deployment failures for a duration of 2 hours, 45 minutes globally. From preliminary analysis, the root cause of the issue was an unexpected increase of requests which caused higher than normal latency and errors.

Customer Impact:

Affected customers experienced elevated serving latency, 500 errors, and deployment failures.

Additional details:

As a workaround, some customers who experienced deployment failures could try redeploying their applications although multiple attempts might have been needed to successfully redeploy.


1 Apr 2023 19:44 PDT

The issue with Cloud Run has been resolved for all affected users as of Saturday, 2023-04-01 19:25 US/Pacific.

We thank you for your patience while we worked on resolving the issue.

1 Apr 2023 18:25 PDT

Summary: Global : Cloud Run is experiencing elevated latency and deployment failures

Description: Our Engineering team identified a fix and mitigation work is currently underway.

We do not have an ETA for mitigation at this point.

We will provide more information by Saturday, 2023-04-01 20:00 US/Pacific.

Diagnosis: Affected customers will experience elevated serving latency, 500 errors and deployment failures.

Workaround:

  • No workarounds at this time for customers experiencing serving latency.

  • Customers who are experiencing deployment failures can try redeploying their applications

1 Apr 2023 18:11 PDT

Summary: Global : Cloud Run is experiencing elevated latency and deployment failures

Description: We are experiencing an issue with Cloud Run beginning at Saturday, 2023-04-01 16:40 US/Pacific.

Our engineering team continues to investigate the issue.

We will provide an update by Saturday, 2023-04-01 18:45 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: Affected customers will experience elevated serving latency, 500 errors and deployment failures.

Workaround:

  • No workarounds at this time for customers experiencing serving latency.

  • Customers who are experiencing deployment failures can try redeploying their applications