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 Google App Engine

AppEngine Flexible users may be experiencing an increase in HTTP 429 responses.

Incident began at 2024-10-09 14:57 and ended at 2024-10-09 17:18 (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)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Warsaw (europe-central2)Belgium (europe-west1)London (europe-west2)Frankfurt (europe-west3)Zurich (europe-west6)Montréal (northamerica-northeast1)São Paulo (southamerica-east1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)

Date Time Description
9 Oct 2024 18:27 PDT

Summary: AppEngine Flexible users may be experiencing an increase in HTTP 429 responses.

Description: The issue with Google AppEngine Flexible has been resolved for all affected users as of Wednesday, 2024-10-09 17:18 US/Pacific.

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

9 Oct 2024 17:52 PDT

Summary: AppEngine Flexible users may be experiencing an increase in HTTP 429 responses.

Description: Mitigation has been applied by our engineering team and we are seeing recovery for impacted users. We will continue to monitor our environment for stability.

If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.

We will provide more information by Wednesday, 2024-10-09 18:30 US/Pacific.

Diagnosis: None at this time.

Workaround: None at this time.