Service Health
Incident affecting Google Cloud Networking
Internal load balancers in us-east1 not updating
Incident began at 2019-08-27 14:34 and ended at 2019-08-27 16:00 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 27 Aug 2019 | 16:00 PDT | The issue with Cloud Networking Internal load balancers in us-east1 not updating has been resolved for all affected projects as of Tuesday, 2019-08-27 15:56 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. |
| 27 Aug 2019 | 15:54 PDT | Description: We are rolling back a potential fixto mitigate this issue. We will provide another status update by Tuesday, 2019-08-27 17:00 US/Pacific with current details. Diagnosis: Affected customers may experience configuration changes not propagating, including health checks for backends. This only affects Internal HTTP(S) Load Balancers. Internal TCP/UDP Load Balancing are not affected. Workaround: None at this time. |
| 27 Aug 2019 | 15:18 PDT | Description: Our Engineering Team believes they have identified the root cause and is working to mitigate. We will provide another status update by Tuesday, 2019-08-27 15:54 US/Pacific with current details. Diagnosis: Affected customers may experience configuration changes not propagating, including health checks for backends. This only affects Internal HTTP(S) Load Balancers. Internal TCP/UDP Load Balancing are not affected. Workaround: None at this time. |
| 27 Aug 2019 | 15:13 PDT | Description: Our Engineering Team believes they have identified the root cause and is working to mitigate. We will provide another status update by Tuesday, 2019-08-27 15:54 US/Pacific with current details. Diagnosis: Affected customers may experience configuration changes not propagating, including health checks for backends. Workaround: None at this time. |
| 27 Aug 2019 | 14:37 PDT | Description: We are investigating errors with Google Cloud Networking, regional internal load balancers in us-east1. Our Engineering Team is investigating possible causes. We will provide another status update by Tuesday, 2019-08-27 15:30 US/Pacific with current details. Diagnosis: Affected customers may experience configuration changes not propagating, including health checks for backends. Workaround: None at this time. |
- All times are US/Pacific