{"id":10029,"date":"2017-09-01T09:14:53","date_gmt":"2017-09-01T08:14:53","guid":{"rendered":"http:\/\/www.devopsonline.co.uk\/?p=10029"},"modified":"2017-09-01T09:15:26","modified_gmt":"2017-09-01T08:15:26","slug":"google-clouds-18-hours","status":"publish","type":"post","link":"https:\/\/devopsnews.online\/google-clouds-18-hours\/","title":{"rendered":"Google in the clouds for 18 hours"},"content":{"rendered":"
Google Cloud\u2019s load balancers suffered a connectivity problem for 18 hours, affecting virtual machines across the US, Europe and Asia.<\/p>\n
The incident was first reported yesterday at 00:52, and was unresolved by 19:18.<\/p>\n
Google wrote in a statement at 06:00: \u201cWe are determined the infrastructure component is responsible for the issue and mitigation work is currently underway.\u201d<\/p>\n
At 08:30 the message changed: \u201cWe have identified the event that triggers this issue and are rolling back a configuration change to mitigate this issue.\u201d<\/p>\n
Google stated it was carrying \u201cfurther measures to completely resolve the issue\u201d, once the change was implemented, half an hour after.<\/p>\n
Afterwards, Google advised users to do the following:<\/p>\n
According to The Register<\/em>, Google admitted that it was source of the issue through an update of its own.<\/p>\n Google also broke its own cloud in April 2016, July 2016, August 2016 and September 2016.<\/p>\n Written by Leah Alger<\/p>\n","protected":false},"excerpt":{"rendered":" Google Cloud\u2019s load balancers suffered a connectivity problem for 18 hours, affecting virtual machines across the US, Europe and Asia<\/p>\n","protected":false},"author":12,"featured_media":10030,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","pmpro_default_level":"","footnotes":""},"categories":[2,1158],"tags":[266,70,1626,81,1906,180,1546,1030,1904,1064,1905],"yoast_head":"\n