Service Health

The issue with Cloud network programming delays and connectivity issues in us-east1 and us-east4, Load balancer health check failures in us-east4-a has been resolved for all affected users as of Tuesday, 2019-06-04 15:30 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.

Our Engineering Team believes they have identified the root cause of the issue and is working to mitigate. Current data indicate(s) that GCE VM creation, live instance migration and any changes to network programming might be delayed. Google Cloud Load Balancer and Internal Load Balancer backends may fail health checking in us-east4-a. Newly created VMs, Cloud VPN and Router in the affected regions may experience connectivity issues. We will provide another status update by Tuesday, 2019-06-04 16:00 US/Pacific with current details.

We are experiencing an issue with Cloud network programming delays in us-east1 and us-east4 and Load balancer health check failures in us-east4-a beginning at Tuesday, 2019-06-04 13.26 US/Pacific. Current data indicate(s) that GCE VM creation, live instance migration and any changes to network programming might be delayed. Google Cloud Load Balancer and Internal Load Balancer backends may fail health checking in us-east4-a. Newly created VMs in the affected regions may experience connectivity issues. For everyone who is affected, we apologize for the disruption. We will provide an update by Tuesday, 2019-06-04 15:30 US/Pacific with current details.

Cloud network programming delays in us-east1 and us-east4 and Load balancer health check failures in us-east4-a.