On June 2nd, Google Cloud faced high level of network congestion in eastern regions of the United States. As a result of which, services which relied on Google Cloud — including Google’s own — faced prolonged downtime. Services like Youtube, Gmail, Discord and even Snapchat were down for a considerable period of time. On the same day at 1:36 pm PT, Google provided update that “We are experiencing high levels of network congestion in the eastern USA, affecting multiple service in Google Cloud, GSuite and YouTube. Users may see slow performance or intermittent errors.”
It seems like this issue has now been addressed and Google is resolved ‘to make appropriate improvements to our systems to help prevent or minimize future recurrence.’ Google in its status update reported that an internal investigation of said matters will be conducted and a detailed report will be provided soon. Google Cloud Platform had to go through two phase recovery to return the services to normal for its consumers. Google’s status update on Google Cloud Platform reported the issues were solved by 4 pm PT.
The close to 5 hours that Google took, to resolve these issues, were clearly enough for the internet hungry populace to vent their frustration out. Hashtags #YouTubeDOWN and #snapchat were trending until the issue was resolved.
YouTube creators weren’t able to upload any videos on the site during this period. A Twitter user Jack Scantlebury tweeted about all the services that were down. Namely, these include not only YouTube, Snapchat, Gmail but also Google Drive, Rocket League, Uber, Uber Eats, Vimeo, Discord, Spectrum, Dauntless and Nest.
Google Cloud is Google’s server platform which means consumers can not only store their data online but also run programs. And Snapchat being one of those consumers, was hence affected by the downtime. Uber was also affected by this network congestion issue.
Users are advised to keep checking the site Downdetector in case of further similar issues. More details on the handled problem can be found here.
As of now, this issue has been resolved.
