Service Health
Incident affecting Google BigQuery
Some BigQuery queries fail with RESOURCE_EXCEEDED errors
Incident began at 2021-06-11 03:34 and ended at 2021-06-15 16:06 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 15 Jun 2021 | 16:06 PDT | Upon further investigation, our engineering teams believe that the scope of the BigQuery issue is now limited to a small number of projects. If you have questions or feel that you may be impacted, please open a case with the Support Team and we will work with you until the issue is resolved. No further updates will be provided here. We thank you for your patience while we're working on resolving the issue. |
| 15 Jun 2021 | 09:14 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. We are evaluating the projects impacted by this issue and performing mitigation as needed. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2021-06-15 16:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 15 Jun 2021 | 09:13 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. We are evaluating the projects impacted by this issue and performing mitigation as needed. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2021-06-15 16:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 15 Jun 2021 | 05:06 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. We are evaluating the projects impacted by this issue and performing mitigation as needed. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2021-06-15 10:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 15 Jun 2021 | 05:01 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. We are evaluating the projects impacted by this issue and performing mitigation as needed. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2021-06-15 10:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 15 Jun 2021 | 02:02 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. We are evaluating the projects impacted by this issue and performing mitigation as needed. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2021-06-15 05:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 14 Jun 2021 | 20:56 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. We are evaluating the projects impacted by this issue and performing mitigation as needed. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2021-06-15 02:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 14 Jun 2021 | 20:55 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. We are evaluating the projects impacted by this issue and performing mitigation as needed. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2021-06-15 02:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 14 Jun 2021 | 16:03 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. We are evaluating the projects impacted by this issue and performing mitigation as needed. We do not have an ETA for full resolution at this point. We will provide an update by Monday, 2021-06-14 21:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 14 Jun 2021 | 09:57 PDT | Summary: Some BigQuery queries fail with RESOURCE_EXCEEDED errors Description: We believe the issue with Google BigQuery is partially resolved. However, mitigation work is still underway by our engineering team. We do not have an ETA for full resolution at this point. We will provide an update by Monday, 2021-06-14 16:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittent |
| 12 Jun 2021 | 18:14 PDT | Summary: Queries fail with RESOURCE_EXCEEDED Description: Summary: Some BigQuery Queries will fail with RESOURCE_EXCEEDED message: We believe the issue with Google BigQuery is partially resolved. However mitigation is still underway for a viable mitigation for now. We do not have an ETA for full resolution at this point. We will provide an update by Monday, 2021-06-14 11:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittently affected. |
| 11 Jun 2021 | 16:41 PDT | Summary: Queries fail with RESOURCE_EXCEEDED Description: Summary:
An example message would be: [RESOURCES_UNAVAILABLE], Reason: code=RESOURCES_UNAVAILABLE message=RESOURCES_EXCEEDED_WITH_CONTEXT: [The query could not be executed in the allotted memory. Peak usage: 101% of limit.\nTop memory consumer(s):\n query parsing and optimization: 12%\n table/storage metadata: 6%\n other/unattributed: 82%\n] We believe the issue with Google BigQuery is partially resolved. However mitigation is still underway for a viable mitigation for now. We do not have an ETA for full resolution at this point. We will provide an update by Saturday, 2021-06-12 13:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: No workarounds. Retries may eventually succeed as the issue seems to be intermittently affected. |
| 11 Jun 2021 | 14:07 PDT | Summary: Queries fail with RESOURCE_EXCEEDED Description: We believe the issue with Google BigQuery is partially resolved. We do not have an ETA for full resolution at this point. We will provide an update by Friday, 2021-06-11 16:30 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: Retrying the job may help but not necessarily immediately. |
| 11 Jun 2021 | 14:04 PDT | Summary: Queries fail with RESOURCE_EXCEEDED Description: We believe the issue with Google BigQuery is partially resolved. We do not have an ETA for full resolution at this point. We will provide an update by Friday, 2021-06-11 16:30 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: Retrying the job may help but not necessarily immediately. |
| 11 Jun 2021 | 13:58 PDT | Summary: Queries fail with RESOURCE_EXCEEDED Description: We believe the issue with Google BigQuery is partially resolved. We do not have an ETA for full resolution at this point. We will provide an update by Friday, 2021-06-11 16:30 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: Retrying the job may help but not necessarily immediately. |
| 11 Jun 2021 | 13:06 PDT | Summary: Queries fail with RESOURCE_EXCEEDED Description: We believe the issue with Google BigQuery is partially resolved. We do not have an ETA for full resolution at this point. We will provide an update by Friday, 2021-06-11 14:00 US/Pacific with current details. Diagnosis: The users will see an error message similar to:
Workaround: Retrying the job may help but not necessarily immediately. |
| 11 Jun 2021 | 11:58 PDT | Summary: Queries fail with RESOURCE_EXCEEDED 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, 2021-06-11 13:06 US/Pacific. Diagnosis: The users will see an error message similar to:
Workaround: Retrying the job may help but not necessarily immediately. |
| 11 Jun 2021 | 06:35 PDT | Summary: Queries fail with RESOURCE_EXCEEDED 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, 2021-06-11 12:06 US/Pacific. Diagnosis: The users will see an error message similar to:
Workaround: Retrying the job may help but not necessarily immediately. |
| 11 Jun 2021 | 06:30 PDT | Summary: Queries fail with RESOURCE_EXCEEDED 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, 2021-06-11 12:06 US/Pacific. Diagnosis: The users will see an error message similar to:
Workaround: Retrying the job may help but not necessarily immediately. |
| 11 Jun 2021 | 05:35 PDT | Summary: Queries fail with RESOURCE_EXCEEDED Description: We are experiencing an intermittent issue with Google BigQuery. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2021-06-11 06:35 US/Pacific with current details. Diagnosis: None at this time. Workaround: Retrying the job may help but not necessarily immediately. |
| 11 Jun 2021 | 03:34 PDT | Summary: Queries fail with RESOURCE_EXCEEDED Description: We are experiencing an intermittent issue with Google BigQuery. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2021-06-11 05:35 US/Pacific with current details. Diagnosis: None at this time. Workaround: None at this time. |
- All times are US/Pacific