Google Cloud Outage Map
The map below depicts the most recent cities worldwide where Google Cloud users have reported problems and outages. If you are having an issue with Google Cloud, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Google Cloud users affected:
Google Cloud Platform, offered by Google, is a suite of cloud computing services that runs on the same infrastructure that Google uses internally for its end-user products, such as Google Search and YouTube.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Uniontown, PA | 1 |
| Gaithersburg, MD | 1 |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Google Cloud Issues Reports
Latest outage, problems and issue reports in social media:
-
Dom Green
(@domgreen) reported
from
Stratford, England
After today's outage of @GCPcloud ... Not able to get to k8s or any info in cloud console, I'm very glad I let someone else host and run my observability 👍
-
Cirrus Labs
(@cirrus_labs) reported
@tsdgeos It seems to be an issue with the FreeBSD Snap image on @GCPcloud. They just updated it. /cc @ed_maste. We’ll think of a workaround in the meantime.
-
Sourav Paul
(@paulsourav) reported
@googlecloud Though I don't have much idea about the details but it sounds like fundamental monitoring issue and certainly could have been avoided. Tough day for Google SRE team.
-
Alex Barlow
(@alexrbarlow) reported
@domgreen @GCPcloud Was this related to the google identify outage? I have to admit I didn’t notice K8S wise
-
Giuseppe Russo
(@Giusepp43605682) reported
@googlecloud Google isn't safety. This society isn't very safety. I will never trust google again
-
Salim B.
(@SalimBcool) reported
@googlecloud I came here for the comment. I was not disappointed ! Makes me wish these down times happened more often...
-
Tom Anderson
(@twocs) reported
@b184xp7 @googlecloud The issue was with authentication, not the sites themselves. You were able to access YouTube via incognito during the service fault.
-
RKB
(@R_Nine_T) reported
@googlecloud That's all it took to sideline YouTube, Gmail and Google Classroom? Apparently this possibility never occurred to anyone at Google...
-
S S R R Perumal
(@sathyaperumal) reported
@googlecloud Few seconds down in data center world is ridiculously long, 45 minutes down is massive for Google scale #GoogleDowntime
-
Ahmed M Raihan
(@AhmedMRaihan) reported
@googlecloud Most appreciated thing is: There are ppl in Google who can fix things without watching an Youtube video on how to fix. n.b. No big tech sentiment was hurt in this tweet :p
-
Matthew Thompson
(@mr_matt_t) reported
@pete_tnt @googlecloud I got the email around the time of the outage. They've been planning this for months, but you can't help but wonder if they're related.
-
Reflective Data
(@reflectivedata) reported
Not sure if related to #googledown but I believe it somehow is. We're seeing some weird behavior/bugs/disconnects/errors within @googlecloud - especially related to the Compute Engine. Anyone else?
-
Ives Laaf
(@ektoplant) reported
@googlecloud ah well simple tiny issue for itself... large scale impact in the system - quota - who had thought about that... must have been fast running in - might have monitoring too - at least fast to recover - interestingly it seems to be a global quota somehow
-
Alexandre Takacs
(@alexandretakacs) reported
@peetm @pete_tnt @googlecloud Indeed ! Issues do obviously happen but storage quota bringing down the whole Google ecosystem... wow 😮
-
thaddydore
(@thaddydore) reported
@googlecloud @Google worst thing could be stackoverflow being down because of google outstage and google engineers trying to use stackoverflow to fix the bug.