1. Home
  2. Companies
  3. Google Cloud
  4. Outage Map
Google Cloud

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

Loading map, please wait...

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:

Less
More
Check Current Status

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
Township of Evan, KS 1
Catania, Sicily 1
Guayaquil, Guayas 1
Mexico City, CDMX 1
Chhindwāra, MP 1
Los Angeles, CA 1
Check Current Status

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:

  • exolete
    Abhinav Pathak (@exolete) reported

    @googlecloud Hi, we have added a new certificate to App Engine for a custom domain, but it has been more than an hour and it has still not been propagated. Is there currently an issue? How long does the propagation take.

  • gsmithw91
    Garrett Smith (@gsmithw91) reported

    @googlecloud billing support case 70049182 I have reached out over 36 times over the past three months to get a refund for a error that Google claimed was their fault

  • Woody2233
    Vincent Defarge (@Woody2233) reported

    @rseroter @googlecloud Identity and registration are a strong foundation. The next challenge is operational context: which service and business outcome can the agent affect, who owns it, and how do we observe or stop it? An agent registry becomes far more useful when it carries that context.

  • cisco_brad
    Brad Bonin (@cisco_brad) reported

    @googlecloud @Gartner_inc Nice recognition. The AI infrastructure space is heating up - execution matters most right now though. Curious how the actual customer deployments play out over the next year or two.

  • TheGodfessional
    Jo-Wins (@TheGodfessional) reported

    @googlecloud @GoogleDeepMind Help, some individuals have been hacking my phones from 2020-2026 even after changing several @Android phones. These individuals seem to be aware of every new android phone I purchase and the hacking still continues. I believe my primary Google ID account has been compromised.

  • 200divesL8r
    200divesL8r (@200divesL8r) reported

    @googlecloud Yeah, your product sucks bro!

  • T2872727
    Triman Kumar Saha (@T2872727) reported

    @gcloudpartners @googlecloud Urgent!!! I need help my Google Account got disabled by automated AI false positive error... this account is so much important to me and there's no human support.... please help Reference case id- 9-6635000040823

  • cisco_brad
    Brad Bonin (@cisco_brad) reported

    @googlecloud Damn, 10,000x scale is wild. That's the kind of compute density that actually changes what's possible in drug discovery. Smart play.

  • der_chuddie
    𝔇𝔢𝔯 ℭ𝔥𝔲𝔡 (@der_chuddie) reported

    Any lawyer on X? I'd like to propose a CAL against @googlecloud @awscloud and @Azure for not enforcing basic outgoing request filtering and wasting everybody resources with the scanning of .***, .env, and wordpress plugins which represents 99% of the bad traffic.

  • sparkyanderson7
    Sparky Anderson (@sparkyanderson7) reported

    @MLB @googlecloud Counts as one run - the same as a 349' HR just over the RF or LF wall down the line at any stadium

  • sumeetweb
    Sumeet (@sumeetweb) reported

    Update: @googlecloud outage caused this.

  • MankaranSInghK2
    Mankaran (@MankaranSInghK2) reported

    @Google @GoogleCloud @sundarpichai I feel ROBBED. I paid for Google Cloud to learn and build, but I’ve been locked out of my Google account for days. My restoration was approved, yet verification still fails. Cloud Support closed my case and sent me in circles.

  • DeportesEnjoyr
    AndrewFreidmanEnthusiast (@DeportesEnjoyr) reported

    @MLB @googlecloud All the sudden he's hitting homers again. Cheating ****.

  • onchainantonio
    Antonio Gomes (@onchainantonio) reported

    @Googlecloud's recent post-quantum roadmap highlights just how complex this migration is. The most honest line in it is about hardware. Google says some physical replacement cycles will run past 2029. This is a company that owns its data centres, its silicon, its browser and its certificate authority. And it still cannot promise the hardware layer is done by the end of the decade. That is the whole migration in one sentence. Post-quantum is a systems programme, not an algorithm swap. Three things in the roadmap that make the point: → Key exchange was the easy part. Hybrid ML-KEM is already live on Google's endpoints. Encryption in transit moves fast because it only needs two parties to agree. → Signatures are the hard part. ML-DSA and SLH-DSA are too large for the existing WebPKI to carry, so Google is testing Merkle Tree Certificates with Chrome and Cloudflare. They did not swap the signature. They redesigned how trust is distributed. → Roots of trust are the slow part. Caliptra, TPM 2.0, OpenTitan for quantum-secure boot. Silicon has a shipping cycle. No software update shortens it. Now remove Google's advantages. No single owner of the stack. No control over the clients. Keys and signatures published permanently the day they were made. That is what a decentralised network is migrating from. It is why "we'll upgrade later" is a much bigger claim there than it sounds. The organisations with the most control are being the most careful about the timeline. Worth sitting with.

  • rookepoole
    Rooke Poole (@rookepoole) reported

    @googlecloud I got connected now but since this automated maybe not help me with the hackathon

Check Current Status