Service Health
Incident affecting Cloud Run, Google App Engine
Cloud Run and App Engine fail to serve some requests in us-east4, northamerica-northeast1 and northamerica-northeast2
Incident began at 2023-10-23 04:02 and ended at 2023-10-23 06:51 (all times are US/Pacific).
Previously affected location(s)
Montréal (northamerica-northeast1)Toronto (northamerica-northeast2)Northern Virginia (us-east4)
Date | Time | Description | |
---|---|---|---|
| 23 Oct 2023 | 06:51 PDT | The issue with Cloud Run, Google App Engine has been resolved for all affected users as of Monday, 2023-10-23 06:46 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 23 Oct 2023 | 05:48 PDT | Summary: Cloud Run and App Engine fail to serve some requests in us-east4, northamerica-northeast1 and northamerica-northeast2 Description: Mitigation work is still underway by our engineering team. Current data indicates that some requests to the impacted regions are still intermittently failing for some specific use-cases. The mitigation is expected to be completed by Monday, 2023-10-23 07:00 US/Pacific. We will provide more information by Monday, 2023-10-23 07:30 US/Pacific. Diagnosis: Cloud Run services and App Engine apps appear unreachable for some requests targeting us-east4, northamerica-northeast1, northamerica-northeast2. This affects only clients using Quick UDP Internet Connections (QUIC) protocol and not falling back to HTTP/2 on a failed handshake. Workaround: Impacted users can use plain HTTP/2 instead of QUIC or Fail over to unaffected region |
| 23 Oct 2023 | 04:54 PDT | Summary: Cloud Run and App Engine fail to serve some requests in us-east4, northamerica-northeast1 and northamerica-northeast2 Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Monday, 2023-10-23 06:00 US/Pacific. Diagnosis: Cloud Run services and App Engine apps appear unreachable for some requests targeting us-east4, northamerica-northeast1, northamerica-northeast2. This affects only clients using Quick UDP Internet Connections (QUIC) protocol and not falling back to HTTP/2 on a failed handshake. Workaround: Impacted users can use plain HTTP/2 instead of QUIC or Fail over to unaffected region |
- All times are US/Pacific