A large Google Cloud loss has reduced the sinks of the internet and even workspace apps -this is what we know
- Advertisement -
- Advertisement -
- Google Cloud Stragage influenced 40 locations, and even Cloudflare
- Spotify, Discord and more went down, just like a few workspace apps
- Google blamed a Dodgy Update for the malfunction, promises to “do better”
A number of popular websites went offline yesterday Google Cloud experienced a major malfunction Which means that users do not have access to Spotify, Discord and Cloudflare for a while.
With the influence of more than 40 locations and 26 services, the failure systems will fall at 11:46 am PT on Thursday 12 June, but at 12.30 pm PT reported that Google was usually resolved, except the US-Central1 (IOWA) region.
The company claimed that it had identified the cause of the problem and that technical teams were working on a recovery, but some users continued to experience PT problems at 12:41 pm.
Google Cloud Stragage takes up popular sites
Although Google Cloud stated that the malfunction started at 11:46 am PT, Cloudflare also experienced disturbances of 11:19 am PT, giving Google Cloud the blaming for the problems.
Among the popular affected sites were Spotify, Discord, Snapchat, Character.ai, Cursor and Replit. Down detector Also shows peaks in the number of complaints of users who are trying to access some Google services, such as Google Maps And YouTube.
According to the Outage Tracker, some workspace apps such as Drive, Docs and measures were also influenced by the malfunction.
“We are very sorry for the impact of all our users and their customers who caused this service disruption/failure. Companies large and small trust Google Cloud with your workloads and we will do better,” the company wrote in the Mini -Incident report.
The report blames an invalid automated quota update of the API management system from Google Cloud for the malfunction and claims almost complete recovery within two hours. Some delays for restoration, however, continued: “Different products had a moderate remaining impact (eg backlogs) to an hour after the primary problem was limited and then recovered a small number.”
A full invoke The incident is available on the Status Website of Google Cloud and the company has promised a full report that follows.
Maybe you like it too
- Advertisement -