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
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:

  • a8hi_b
    Abhi Balijepalli (@a8hi_b) reported

    @googlecloud Trying to get a hold of you guys, hitting quotas and having outages. Plz help.

  • DeportesEnjoyr
    AndrewFreidmanEnthusiast (@DeportesEnjoyr) reported

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

  • Aka_olisa_
    Aka4real (@Aka_olisa_) reported

    @googlecloud Why this matters for Google: Developers and early-stage startups are being forced to migrate to competitors (like AWS, which has introduced local NGN billing support) simply because we cannot physically pay Google.

  • MarizMelo
    Mariz (@MarizMelo) reported

    @googlecloud forcing users into prepaid sucks. Maybe time to look for alternatives to host your #AI product :/

  • jakob_btc
    Jakob (@jakob_btc) reported

    The privacy paradox of the AI era is that utility requires intimacy. To make an AI agent genuinely useful, you have to give it access to proprietary context: internal knowledge, emails, code, workflows. Generic data does not get you very far. So what happens to privacy when hiding the data is no longer realistic? My view is that the privacy stack is shifting from data redaction to verifiable processing. Three major shifts happening right now: 1. Confidential AI at Scale: We’re moving past relying on corporate promises. @googlecloud recently rolled out Confidential G4 VMs with NVIDIA Blackwell GPUs. The tech is mainstreaming. With hardware-based Trusted Execution Environments, your knowledge base is encrypted in memory while the model processes it. Even the cloud provider can’t peek 2. End-to-End Prompt Encryption: Infinite AI memory is a privacy nightmare. The next wave of tools will use localized, cryptographic session gates. Google again recently open-sourced Prompt Encryption SDKs to tackle this problem, establishing a secure channel that keeps data encrypted from the client all the way until it hits the secure chip, before the session vanishes 3. Local Middleware & Edge SLMs: Instead of sending everything blindly to centralized frontier models, enterprises are routing data through local semantic firewalls The bottom line: You will feed AI everything it needs to know, but the tech stack will make sure the vendor never actually "learns" or retains a single byte of it.

  • PizzaBoiPiazza
    Mikey Pizza (@PizzaBoiPiazza) reported

    @MLBStats @googlecloud @Mets HANG THE BANNER

  • gsmithw91
    Garrett Smith (@gsmithw91) reported

    @googlecloud @ThomasOrTK What is the magic number of follow ups and requests someone has to do to get resolution for billing support? Its beyond 30 at this point.

  • dick41259892
    Caffeinated Acrimony (@dick41259892) reported

    @googlecloud Pajeet ceo? No thanks. The software is for sure total ****.

  • ramiakeela
    Rami (@ramiakeela) reported

    Today, @NeraSystems and @googlecloud are announcing partnership. Regulated orgs can now run @GeminiApp on their most sensitive data, client financials, patient records, proprietary datasets, without ever exposing it to the model. The LLM gets the query. It never gets the data.

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

  • valenvp03
    Valentina Valdes (@valenvp03) reported

    @googlecloud This is where enterprise AI gets serious: domain skills, governed connectors and traceable outputs. The chatbot layer was never going to be enough for legal work.

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

  • ParagBatham
    Parag Dher Sare Paise Wala (@ParagBatham) reported

    @GoogleCloud I need urgent help with a disputed Google Cloud billing charge. I've tried getting through Google Cloud Billing Support, but the automated assistant won't connect me with a human. Please help me get this escalated to a billing specialist. I can provide the details

  • cisco_brad
    Brad Bonin (@cisco_brad) reported

    @googlecloud Code review becoming the actual bottleneck is wild. Guess we're trading one problem for another, but at least the hard part (ideation) moves faster. Need smarter filtering before human eyes touch it.

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

Check Current Status