![](\"http:\/\/www.cloudcomputing-news.net\/media\/img\/news\/iStock_google1423_kAY44up.jpg.300x150_q96.png\")
<\/p>\n<\/p>\n
(c)iStock.com\/tarik kizilkiya<\/em><\/p>\n Google’s infrastructure as a service (IaaS) offering Compute Engine lost connectivity across all regions for 18 minutes on April 11 after problems experienced with a bug in its network configuration management software.<\/p>\n In a status update discussing the outage and how it occurred posted yesterday, the search giant confirmed the event affected Compute Engine only, and bemoaned how its ‘canary step’ process – a configuration deployed to a single site to ensure there are no issues with upstream failures – had a software bug. The result was that the push system wrongly believed there were no issues with the new configuration, and therefore happily began its rollout resulting in dropped traffic.<\/p>\n “The Google engineers who had been investigating a localised failure of the asia-east1 VPN now knew that they had a widespread and serious problem,” a post<\/a> from Benjamin Treynor Sloss, the interestingly titled ‘VP 24×7’ at Google, reads. “They did precisely what we train for, and decided to revert the most recent configuration changes made to the network even before knowing for sure what the problem was.<\/p>\n “This was the correct action, and the time from detection to decision to revert to the end of the outage was thus just 18 minutes,” Sloss adds.<\/p>\n Naturally Google has apologised to its customers, and has also thrown in discounts of service credits up to 25% of impacted Compute Engine and VPN applications for those affected ‘to underscore how seriously we are taking this event.’ Previously, Google’s cloud has fallen over due to a connectivity fault<\/a> in February last year, and an issue with manual link activation<\/a> back in November.<\/p>\n Google says that the latest issue is under control meaning there is no risk of a reoccurrence, while its engineering teams will be working on prevention, detection, and mitigation systems over the next ‘several weeks’ to aim to ensure this sort of thing won’t happen again.<\/p>\n","protected":false},"excerpt":{"rendered":" (c)iStock.com\/tarik kizilkiya
\nGoogle’s infrastructure as a service (IaaS) offering Compute Engine lost connectivity across all regions for 18 minutes on April 11 after problems experienced with a bug in its network configuration management softwa…<\/p>\n","protected":false},"author":50,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-21841","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/21841","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/users\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/comments?post=21841"}],"version-history":[{"count":3,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/21841\/revisions"}],"predecessor-version":[{"id":22842,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/21841\/revisions\/22842"}],"wp:attachment":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/media?parent=21841"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/categories?post=21841"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/tags?post=21841"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}