The global outage has raised concerns about the reliability of public cloud services, with ServerChoice commercial director Adam Bradshaw saying they are “not a silver bullet for IT infrastructure”. “We have identified a probable root cause and will be publishing an incident report within the next several days,” Google said. Google Cloud’s Status Dashboard yesterday said an issue with Traffic Director was caused by a “recent release”, which was rolled back following the incident. “In its malfunction, it caused our internal load balancing layer to not have a valid configuration, which caused a loss of availability of the API.” “Engineering has root-caused this issue to a Google Cloud component called Traffic Director, which is responsible for configuring our load balancing layer,” Discord said in its report. While Spotify did not give details of its outage, a case study from Google suggests that Spotify is a customer of its cloud services. The issue has been linked to Google Cloud, with Discord referencing Google Cloud as the cause in its incident report.
Thanks for your reports!Ī couple of hours after Spotify and Discord shared the issue online, both companies reported that their systems had returned to normal.īased on Discord’s incident report, the increase in errors was noticed at around 9am Pacific Standard Time and was resolved by around 1pm.Ĭybersecurity watchdog Netblocks said that Twitter also suffered “intermittent failures” at around this same time, while some users said they were unable to access Wikipedia. Something’s not quite right, and we’re looking into it. Multiple sites including Spotify and Discord suffered outages yesterday (8 March), becoming unavailable for many users around the world.īoth companies confirmed outages on Twitter after users reported being unable to properly connect to these platforms. The incident raised questions about public cloud reliability as it is believed the cause of the global outages stemmed from Google Cloud.
0 kommentar(er)
