Incident affecting Eventarc
Issue with Eventarc
Incident began at 2021-11-12 00:30 and ended at 2021-11-12 02:14 (all times are US/Pacific).
| ||12 Nov 2021||16:36 PST|| |
We apologize for the inconvenience this service disruption/outage may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. If you have experienced impact outside of what is listed below, please reach out to Google Support by opening a case using https://cloud.google.com/support.
(All Times US/Pacific)
Incident Start: 12 November 2021 00:30
Incident End: 12 November 2021 02:14
Duration: 1 hour 44 minutes
Affected Services and Features:
Google’s Front End load balancing service experienced failures resulting in impact to several downstream Google Cloud services in Europe. From preliminary analysis, the root cause of the issue was caused by a new infrastructure feature triggering a latent issue within internal network load balancer code.
The error was caught within 4 minutes by automated safety systems, and further spread was slowed at this point. The issue was fully mitigated approximately 1hr 44m later, when our engineering team completed a rollout to disable the vulnerable code path. The issue will be fully prevented going forward via a root cause fix, which will complete rollout by 12 November 2021 21:00 US/Pacific.
| ||12 Nov 2021||03:47 PST|| |
The issue with Google Cloud infrastructure components has been resolved for all affected products as of Friday, 2021-11-12 03:38 US/Pacific.
If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.
We thank you for your patience while we worked on resolving the issue.
| ||12 Nov 2021||01:57 PST|| |
Summary: Issue with Eventarc
Description: beginning at Friday, 2021-11-12 00:36 US/Pacific US/Pacific We are experiencing an issue with Google Cloud components.
Our engineering team continues to investigate the issue.
For regular status updates, please follow: https://status.cloud.google.com/incidents/1xkAB1KmLrh5g3v9ZEZ7
Diagnosis: None at this time
Workaround: None at this time