Service Health
Incident affecting Google BigQuery
BigQuery customers may experience "resources exceeded" errors during query execution
Incident began at 2023-03-06 14:03 and ended at 2023-03-07 22:24 (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)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)Milan (europe-west8)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)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)
Date | Time | Description | |
---|---|---|---|
| 7 Mar 2023 | 22:24 PST | The issue with Google BigQuery has been resolved for all affected users as of Tuesday, 2023-03-07 20:53 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 7 Mar 2023 | 14:50 PST | Summary: BigQuery customers may experience "resources exceeded" errors during query execution Description: We believe that the issue with Google BigQuery is partially resolved. Full resolution is expected to be completed by Wednesday, 2023-03-08 17:00 US/Pacific. We will provide an update by Wednesday, 2023-03-08 17:30 US/Pacific with current details. Diagnosis: Affected customers may experience "resources exceeded" error during query execution. Workaround: None at this time. |
| 6 Mar 2023 | 20:46 PST | Summary: BigQuery customers may experience "resources exceeded" errors during query execution Description: We believe that the issue with Google BigQuery is partially resolved. Full resolution is expected to be completed by Wednesday, 2023-03-08 17:00 US/Pacific. We will provide an update by Tuesday, 2023-03-07 17:00 US/Pacific with current details. Diagnosis: Affected customers may experience "resources exceeded" error during query execution. Workaround: None at this time. |
| 6 Mar 2023 | 19:49 PST | Summary: BigQuery customers may experience "resources exceeded" errors during query execution Description: Mitigation work by our engineering team is still in progress. We do not have an ETA for mitigation at this point. We will provide more information by Monday, 2023-03-06 21:00 US/Pacific. Diagnosis: Affected customers may experience "resources exceeded" error during query execution. Workaround: None at this time. |
| 6 Mar 2023 | 15:03 PST | Summary: BigQuery customers may experience "resources exceeded" errors during query execution Description: Mitigation work by our engineering team is in progress. We do not have an ETA for mitigation at this point. We will provide more information by Monday, 2023-03-06 20:00 US/Pacific. Diagnosis: Affected customers may experience "resources exceeded" error during query execution. Workaround: None at this time. |
| 6 Mar 2023 | 14:33 PST | Summary: BigQuery customers may experience "resources exceeded" errors during query execution 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-03-06 15:41 US/Pacific. Diagnosis: Affected customers may experience resources exceeded error during query execution. Workaround: None at this time. |
| 6 Mar 2023 | 14:25 PST | Summary: BigQuery customers may experience "resources exceeded" errors during query execution Description: We are experiencing an issue with Google BigQuery beginning at Monday, 2023-03-05 03:02 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2023-03-06 15:31 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Affected customers may experience resources exceeded error during query execution. Workaround: None at this time. |
- All times are US/Pacific