Google Cloud MAJOR
We are experiencing Cloud Networking Control Plane issues
April 26, 2022 · 09:47 AM UTC – 10:40 AM UTC · Duration: 53min
Affected Services
Google Cloud NetworkingCloud Load Balancing
Timeline
06:23 PM
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 https://cloud.google.com/support or help article https://support.google.com/a/answer/1047213.
(All Times US/Pacific)
Incident Start: 26 April 2022 01:47
Incident End: 26 April 2022 02:40
Duration: 53 minutes
Affected Services and Features: Google Cloud Networking
Regions/Zones: Global/All regions
Description:
Google Cloud Networking control plane experienced elevated latency. All Google Cloud Load Balancer config to Google Front End stalled globally for a duration of 53 minutes.From the preliminary analysis, the root cause of the issue seems to be a race condition where unprocessed configuration deletes caused conflicts with newer configuration changes, leading to the configuration pipeline stall.
Customer Impact:
Customers might have experienced issues while creating new forwarding rules for Global Layer 7 External load balancer or edit or delete existing ones.
10:52 AM
The issue with Google Cloud Networking has been resolved for all affected users as of Tuesday, 2022-04-26 02:40 US/Pacific.
We thank you for your patience while we worked on resolving the issue.
10:32 AM
Summary: We are experiencing Cloud Networking Control Plane issues
Description: We are experiencing an issue with Google Cloud Networking beginning at Tuesday, 2022-04-26 02:06 US/Pacific.
Our engineering team continues to investigate the issue.
We will provide an update by Tuesday, 2022-04-26 03:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: None at this time.
Workaround: None at this time.