Google Cloud Status Dashboard

This page provides status information on the services that are part of Google Cloud Platform. 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 cloud.google.com.

Google Compute Engine Incident #16014

HTTP(S) Load Balancing returning some 502 errors

Incident began at 2016-07-29 08:45 and ended at 2016-07-29 14:43 (all times are US/Pacific).

Date Time Description
Jul 29, 2016 15:06

The issue with HTTP(S) Load Balancing returning 502 errors was mitigated as of 2016-07-29 14:43 US/Pacific.

The issue with HTTP(S) Load Balancing returning 502 errors was mitigated as of 2016-07-29 14:43 US/Pacific.

Jul 29, 2016 14:37

The issue with HTTP(S) Load Balancing is still ongoing. We are currently working with effected customers to mitigate, however customers who have not already experienced this issue should not be effected. We are continuing to investigate the problem, and will provide an update by 15:00 US/Pacific.

The issue with HTTP(S) Load Balancing is still ongoing. We are currently working with effected customers to mitigate, however customers who have not already experienced this issue should not be effected. We are continuing to investigate the problem, and will provide an update by 15:00 US/Pacific.

Jul 29, 2016 11:10

We are experiencing an issue with HTTP(S) Load Balancing returning a small number 502 errors, beginning at Friday, 2016-07-29 around 08:45 US/Pacific.

The maximum error rate for affected users was below 2%. Remediation has been applied that should stop these errors; we are monitoring the situation.

For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide an update by 11:30 US/Pacific with current details.

We are experiencing an issue with HTTP(S) Load Balancing returning a small number 502 errors, beginning at Friday, 2016-07-29 around 08:45 US/Pacific.

The maximum error rate for affected users was below 2%. Remediation has been applied that should stop these errors; we are monitoring the situation.

For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide an update by 11:30 US/Pacific with current details.