Service Health
Incident affecting Google Cloud Pub/Sub
Internal errors and latency on ordered Publish
Incident began at 2023-08-04 04:28 and ended at 2023-08-04 05:30 (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)Doha (me-central1)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 | |
---|---|---|---|
| 4 Aug 2023 | 05:30 PDT | The issue with Google Cloud Pub/Sub has been resolved for all affected users as of Friday, 2023-08-04 05:29 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 4 Aug 2023 | 04:55 PDT | Summary: Internal errors and latency on ordered Publish 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 Friday, 2023-08-04 06:00 US/Pacific. Diagnosis: Customers are experiencing increased latency and an increased rate of internal server errors for Publish requests using ordering keys. Workaround: None at this time. |
- All times are US/Pacific