Google Cloud
Google Cloud Platform lets you build and host applications and websites, store data, and analyze data on Google's scalable infrastructure.
Homepage: https://cloud.google.com/
Status Page: https://status.cloud.google.com/
Open Incidents
No open incidents
Scheduled Incidents
No scheduled incidents
Previous Incidents
New VMs are experiencing connectivity issues
2017-01-30 19:13:24| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-30 20:56:32 | We have fully mitigated the network connectivity issues for newly-created GCE instances as of 12:45 US/Pacific, with VPNs connectivity issues being fully mitigated at 12:50 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. We will provide a more detailed analysis of this incident once we have completed our internal investigation. |
| Update | 2017-01-30 20:40:02 | The issue with newly-created GCE instances experiencing network connectivity problems should have been mitigated for all GCE regions except europe-west1, which is currently clearing. Newly-created VPNs are additionally affected; we are still working on a mitigation for this. We will provide another status update by 13:10 US/Pacific with current details. |
| Update | 2017-01-30 20:07:00 | The issue with newly-created GCE instances experiencing network connectivity problems should have been mitigated for the majority of GCE regions and we expect a full resolution in the near future. We will provide another status update by 12:40 US/Pacific with current details. |
| Update | 2017-01-30 19:40:43 | We are experiencing a connectivity issue affecting newly-created VMs, as well as those undergoing live migrations beginning at Monday, 2017-01-30 10:54 US/Pacific. Mitigation work is currently underway. All zones should be coming back online in the next 15-20 minutes. For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide another update at 12:10 PST. |
| Update | 2017-01-30 19:13:24 | We are investigating an issue with newly-created VMs not having network connectivity. This also affects VMs undergoing live migrations. We will provide more information by 11:45 US/Pacific. |
Bigquery query job failures
2017-01-21 08:06:22| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-21 16:09:53 | The issue with BigQuery's Table Copy service and query jobs should have been resolved for all affected projects as of 07:30 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence |
| Update | 2017-01-21 14:13:25 | The issue with BigQuery's Table Copy service and query jobs should be resolved for majority of users and expect a full resolution in the near future. We will provide another status update by 08:00 US/Pacific, 2017-01-21. |
| Update | 2017-01-21 12:02:42 | We believe the issue with BigQuery's Table Copy service and query jobs should be resolved for majority of users and expect a full resolution in the near future. We will provide another status update by 06:00 US/Pacific, 2017-01-21. |
| Update | 2017-01-21 09:50:19 | We believe the issue with BigQuery's Table Copy service and query jobs should be resolved for majority of users and expect a full resolution in the near future. We will provide another status update by 04:00 US/Pacific, 2017-01-21. |
| Update | 2017-01-21 08:06:22 | We are experiencing an issue with Bigquery query jobs beginning at Friday, 2017-01-21 18:15 US/Pacific. |
BigQuery Web UI currently unavailable for some Customers
2017-01-10 13:29:51| Action | Date | Description |
|---|---|---|
| Update | 2017-01-10 14:00:11 | The issue with BigQuery Web UI should have been resolved for the majority of users and we expect a full resolution in the near future. We will provide another status update by 06:30 US/Pacific with current details. |
| Resolved | 2017-01-10 14:00:11 | The issue with BigQuery Web UI should have been resolved for the majority of users and we expect a full resolution in the near future. We will provide another status update by 06:30 US/Pacific with current details. |
| Update | 2017-01-10 13:29:51 | We are investigating an issue with BigQuery Web UI. We will provide more information by 2017-01-10 06:00 US/Pacific. |
Issues with Compute Engine serial port output and Cloud Shell
2017-01-09 02:06:21| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-09 06:45:00 | The issues with Cloud Shell and Compute Engine serial output should have been resolved for all affected instances as of 22:25 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
| Update | 2017-01-09 06:00:00 | The issue with Cloud Shell should be resolved for all customers at this time. The issue with Compute Engine serial port output should be resolved for all new instances created after 19:45 PT in all zones. Instances created before 14:10 PT remain unaffected. Some instances created between 14:10 and 19:45 PT in us-east1-c and us-west1 may still be unable to view the serial output. We are currently in the process of applying the fix to zones in this region. Access to the serial console output should be restored for instances created between 14:10 and 19:45 PT in all other zones. We expect a full resolution in the near future. We will provide another status update by 23:00 US/Pacific with current details. |
| Update | 2017-01-09 05:00:00 | The issue with Cloud Shell should be resolved for all customers at this time. The issue with Compute Engine serial port output should be resolved for all new instances created after 19:45 PT in all zones. Instances created before 14:10 PT remain unaffected. Access to the serial console output should be restored for all instances in the asia-east1 and asia-northeast1 regions, and the us-central1-a zone, created between 14:10 and 19:45 PT. Some instances created between 14:10 and 19:45 PT in other zones may still be unable to view the serial console output. We are currently in the process of applying the fix to the remaining zones. We expect a full resolution in the near future. We will provide another status update by 22:00 US/Pacific with current details. |
| Update | 2017-01-09 04:00:00 | The issue with Cloud Shell should be resolved for all customers at this time. The issue with Compute Engine serial port output should be resolved for all new instances created after 19:45 PT, and all instances in us-central1-a, and asia-east1-b created between 14:10 and 19:45 PT. All other instances created before 14:10 PT remain unaffected. We expect a full resolution in the near future. We will provide another status update by 21:00 US/Pacific with current details. |
| Update | 2017-01-09 03:00:00 | We are still investigating the issues with Compute Engine and Cloud Shell, and do not have any news at this time. We will provide another status update by 20:00 US/Pacific with current details. |
| Update | 2017-01-09 02:06:21 | We are experiencing issues with Compute Engine serial port output and Cloud Shell beginning at Sunday, 2017-01-08 14:10 US/Pacific. Current data indicates that newly-created instances are unable to use the "get-serial-port-output" command in "gcloud", or use the Cloud Console to retrieve serial port output. Customers can still use the interactive serial console on these newly-created instances. Instances created before the impact time do not appear to be affected. Additionally, the Cloud Shell is intermittently available at this time. For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide an update by 19:00 US/Pacific with current details. |
Cloud VPN issues in regions us-west1 and us-east1
2017-01-04 07:22:48| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-04 07:55:57 | The issue with Cloud VPN where some tunnels werent connecting in us-east1 and us-west1 should have been resolved for all affected tunnels as of 23:45 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
| Update | 2017-01-04 07:22:48 | We are investigating reports of an issue with Cloud VPN in regions us-west1 and us-east1. We will provide more information by 23:45 US/Pacific. |
Cloud Storage is showing inconsistent result for object listing for multi-regional buckets in US
2016-12-20 06:52:16| Action | Date | Description |
|---|---|---|
| Update | 2016-12-20 09:59:34 | The issue with Cloud Storage showing inconsistent results for object listing for multi-regional buckets in US should have been resolved for all affected projects as of 23:50 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
| Update | 2016-12-20 07:59:13 | We are still investigating the issue with Cloud Storage showing inconsistent result for object listing for multi-regional buckets in US. We will provide another status update by 2016-12-20 02:00 US/Pacific with current details. |
| Resolved | 2016-12-20 07:59:13 | We are still investigating the issue with Cloud Storage showing inconsistent result for object listing for multi-regional buckets in US. We will provide another status update by 2016-12-20 02:00 US/Pacific with current details. |
| Update | 2016-12-20 06:52:16 | We are experiencing an intermittent issue with Cloud Storage showing inconsistent result for object listing for multi-regional buckets in US beginning approximately at Monday, 2016-12-16 09:00 US/Pacific. For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide an update by 2016-12-17 00:00 US/Pacific with current details. |
Elevated Cloud Storage error rate and latency
2016-12-11 17:27:32| Action | Date | Description |
|---|---|---|
| Update | 2016-12-11 18:30:50 | We are continuing experience an issue with Google Cloud Storage. Errors and latency have decreased, but are not yet at pre-incident levels. We are continuing to investigate mitigation strategies and identifying root cause. Impact is limited to the US region. For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide an update by 12:00 US/Pacific with current details. |
| Resolved | 2016-12-11 18:30:50 | We are continuing to experience an issue with Google Cloud Storage. Errors and latency have decreased, but are not yet at pre-incident levels. We are continuing to investigate mitigation strategies and identify root cause. Impact is limited to the US region. For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide an update by 12:00 US/Pacific with current details. |
| Update | 2016-12-11 17:27:32 | We are investigating an issue with Google Cloud Storage serving increased errors and at a higher latency. We will provide more information by 10:30 US/Pacific. |
App Engine remote socket API errors in us-central region
2016-12-03 02:11:18| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-03 11:08:28 | The issue with App Engine applications having higher than expected socket API errors should have been resolved for all affected applications as of 22:00 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
| Update | 2016-12-03 05:05:08 | We are still investigating reports of an issue with App Engine applications having higher than expected socket API errors if they are located in the us-central region. We will provide another status update by 2016-12-02 22:00 US/Pacific with current details. |
| Update | 2016-12-03 04:10:13 | We are still investigating reports of an issue with App Engine applications having higher than expected socket API errors if they are located in the us-central region. We will provide another status update by 2016-12-02 21:00 US/Pacific with current details. |
| Update | 2016-12-03 03:46:00 | The issue with App Engine remote socket API errors in us-central region should have been resolved for all affected projects as of 19:46 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
| Update | 2016-12-03 03:05:04 | We are still investigating reports of an issue with App Engine applications having higher than expected socket API errors if they are located in the us-central region. We will provide another status update by 2016-12-02 20:00 US/Pacific with current details. |
| Update | 2016-12-03 02:11:18 | We are investigating reports of an issue with App Engine applications having higher than expected socket API errors if they are located in the us-central region. We will provide another status update by 2016-12-02 19:00 US/Pacific with current details. |
Increased 500 error rate for BigQuery API calls
2016-11-30 18:31:35| Action | Date | Description |
|---|---|---|
| Resolved | 2016-11-30 18:31:35 | The issue with increased 500 errors from the BigQuery API has been resolved. We apologize for the impact that this incident had on your application. |
BigQuery Streaming API failing
2016-11-09 01:28:52| Action | Date | Description |
|---|---|---|
| Resolved | 2016-11-09 04:00:05 | We're continuing to work to restore the service to the BigQuery Streaming API. We will add an update at 20:30 US/Pacific with further information. |
| Update | 2016-11-09 03:44:04 | We are continuing to investigate the issue with BigQuery Streaming API. We will add an update at 20:00 US/Pacific with further information. |
| Update | 2016-11-09 03:00:00 | We have taken steps to mitigate the issue, which has led to some improvements. The issue continues to impact the BigQuery Streaming API and tables with a streaming buffer. We will provide a further status update at 19:30 US/Pacific with current details |
| Update | 2016-11-09 02:30:00 | We are continuing to investigate the issue with BigQuery Streaming API. The issue may also impact tables with a streaming buffer, making them inaccessible. This will be clarified in the next update at 19:00 US/Pacific with current details. |
| Update | 2016-11-09 02:00:00 | We are still investigating the issue with BigQuery Streaming API. There are no other details to share at this time but we are actively working to resolve this. We will provide another status update by 18:30 US/Pacific with current details. |
| Update | 2016-11-09 01:30:00 | We are still investigating the issue with the BigQuery Streaming API. Current data indicates that all projects are affected by this issue. We will provide another status update by 18:00 US/Pacific with current details. |
| Update | 2016-11-09 01:28:52 | We are investigating an issue with the BigQuery Streaming API. We will provide more information by 17:30 US/Pacific. |