1. Home
  2. ❯
  3. Companies
  4. ❯
  5. Google Cloud
  6. ❯
  7. 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
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:

  • Aritan_lover
    Aritan (@Aritan_lover) reported

    @googlecloud Dear @Google, I’ve paid a significant amount for your services and now face a serious financial issue. For more than 10 days, I’ve tried to reach a human support agent, but there is no clear way to do so. Please review this urgently and connect me with a specialist.

  • jos3gajal
    Robin🍉 (@jos3gajal) reported

    @sammathews @googlecloud HHAHAHA good one, Sam. Now, really, let's stop the jokes and tell us what are you going to do to fix CS2, LoL, Valo, APEX and R6

  • LukasPetrasch
    Lukas Petrasch (@LukasPetrasch) reported

    7 months. 20+ status updates. 8 different support reps. Still no decision. That's our experience with @GoogleCloud Billing following a DDoS incident. I'm genuinely starting to question whether this is the standard a cloud provider of this size holds itself to. #GoogleCloud

  • bally_kehal
    Bally_AgenticAI (@bally_kehal) reported

    Google's Agent Identity gives each agent a SPIFFE ID and a token bound by mTLS to the runtime that issued it. Steal the credential and it won't replay anywhere else. Shared service accounts for agents were always a placeholder. @googlecloud #AgenticAI #IAM

  • virajkokane_
    Viraj Kokane (@virajkokane_) reported

    .@GoogleCloud @GoogleStartups @ragingdas We've been blocked for over 2 weeks trying to get a GPU quota approved for our production workloads. Every manual quota request is auto-rejected within seconds, with no explanation. Our assigned account manager has been unavailable for over a week, with no replacement. We've spoken to 3 different sales contacts, shared all requested details multiple times, and followed up repeatedly. Yet no meaningful update. Our platform has paying customers, and our render pipeline is effectively down because we can't provision the GPUs we need. We're not asking for special treatment - just a human review, transparency, and a point of contact who can help resolve this. We joined the Google for Startups program to build, not to spend weeks chasing responses. Can someone from the Google Cloud team please look into this?

  • ofPowerofWant
    ofPowerofWant (@ofPowerofWant) reported

    I cannot access @googlecloud, that was your choice. Stop sending me emails for someone elses account that they attached me to... fix it or i will make it a public issue that you are sending me someone elses accounts financial information They had no clue they were delinquent lol

  • 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.

  • shayanrm
    Shayan Mashatian (@shayanrm) reported

    @googlecloud What’s the point of replying to messages here, asking DM you with a case number, to send a auto-reply privately that your case is under review?! We know the cases are under review and the issue is that they are not getting resolved fast enough. Why wasting our time to send the case to you in DM if you have an AI just to send an auto-response to it with no new or valuable information? @sundarpichai

  • therealZOAT
    Zachary Rand (@therealZOAT) reported

    @testingcatalog My company's Gemini Enterprise UI never looks like what you or @googlecloud post.

  • sky_vst
    Gleb Otochkin (@sky_vst) reported

    @MShteyn5470 @rseroter @googlecloud Out of curiosity - how would you warm up a public global service endpoint? It serves thousands requests per second all the time and you never really know what backend serves your particular request.

  • abzalgylymbai
    abzal gylymbai (@abzalgylymbai) reported

    @googlecloud Recurring unexplained charges (~$83, repeating) on my Google Cloud Billing account despite no active projects showing in Console. Already paid multiple times, keeps reappearing. No response from support for days. Billing ID: 01B3C0-1899D2-F0DA8D.

  • tanikku
    nik (@tanikku) reported

    @sammathews @Vikxngr @googlecloud Yeah shut down the whole org bruh this is so embarrasing

  • osorioleomar
    Leomar Osorio (@osorioleomar) reported

    Hi @askgcp @googlecloud, our CPTO has paused our company's GCP migration after a known Firebase API vulnerability led to 19k SEK in unauthorized Gemini charges. We provided proof of external abuse but haven't heard back in over a week. Need immediate help with Case #72859549

  • muyang14756529
    身是业的根 (@muyang14756529) reported

    @sundarpichai @GoogleWorkspace The Trust & Safety team is completely cold & irresponsible. They just sent a generic 48-72hr weekend template while knowing my countdown is in HOURS. Absolute zero empathy for small businesses. Help Ticket 2XWJSBKNPMM7QOD3U5KVHZU5WI! @GoogleCloud

  • PizzaBoiPiazza
    Mikey Pizza (@PizzaBoiPiazza) reported

    @MLBStats @googlecloud @Mets HANG THE BANNER

Check Current Status