Console

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 BigQuery

We are experiencing issues with Google BigQuery in the asia-east1 and asia-east2 regions as of Thursday, 2020-03-26 16:53 US/Pacific.

Incident began at 2020-03-26 16:53 and ended at 2020-03-26 18:42 (all times are US/Pacific).

Date Time Description
26 Mar 2020 18:42 PDT

The issue with Google BigQuery has been resolved for all affected projects as of Thursday, 2020-03-26 17:40 US/Pacific.

We thank you for your patience while we've worked on resolving the issue.
26 Mar 2020 17:32 PDT

Description: We are experiencing issues with Google BigQuery in the asia-east1 and asia-east2 regions as of Thursday, 2020-03-26 16:53 US/Pacific.

Affected customers may experience an elevated error rate (up to 100%) when submitting dataset insertion operations.

Our engineers have determined this issue to be linked to a single Google incident. For regular status updates, please visit https://status.cloud.google.com/incident/zall/20003. An update will be posted here by Thursday, 2020-03-26 21:00 US/Pacific.

Diagnosis: Affected customers may experience an elevated error rate (up to 100%) when submitting dataset insertion operations.

Workaround: None at this time.
26 Mar 2020 17:04 PDT

Description: We are experiencing issues with Google BigQuery in the asia-east1 and asia-east2 regions as of Thursday, 2020-03-26 16:53 US/Pacific.

Affected customers may experience an elevated error rate (up to 100%) when submitting dataset insertion operations.

We will provide more information by Thursday, 2020-03-26 17:30 US/Pacific.

Diagnosis: Affected customers may experience an elevated error rate (up to 100%) when submitting dataset insertion operations.

Workaround: None at this time.