This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Google Cloud Has Disruption, Bringing Snapchat, Spotify Down

Issues with Google's cloud service disrupted some popular applications, including Snapchat and Spotify, Tuesday
• The outage was resolved less than an hour after it started
• Google hasn't explained the cause of the issue, but a status report points to a problem with the global load balancing service

(Bloomberg) -- Portions of Google’s cloud-computing service went down Tuesday, leading to the temporary failure of some popular applications that rely on the technology giant, including Snapchat and Spotify. The disruption affected Google’s service that provides computing storage and data management tools for companies.

“We are aware of issues affecting some of our GCP services and the team is actively investigating,” a spokesman for Alphabet Inc.’s Google said in a statement. Less than an hour after the initial reports, the spokesman said the issues “should be resolved” as of 12:48 p.m. San Francisco time.

The outage hit Google a day after extended service issues for Amazon.com Inc. The two companies, along with Microsoft Corp., are the largest providers of data storage over the internet. Some problems on Spotify were fixed within an hour, according to the website Downdetector.com, which tracks outages.

“Something’s not quite right, and we’re looking into it,” Spotify tweeted from the account @SpotifyStatus during the service issue. “Thanks for your reports!”

(Data Center Knowledge) -- It's unclear what exactly caused the outage, but there's a report of an incident on the Google Cloud Status Dashboard that roughly corresponds with its time frame.

There was a networking issue associated with Google Cloud Global Load Balancing, the service that automatically distributes customers' application workloads across servers or data centers to ensure no single resource is being overworked to the point of failure or degraded performance.

Google engineers were still investigating the root cause of the issue as of Wednesday afternoon US Pacific Time.