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

  • CEOinterview
    CEOInterviews.AI (@CEOinterview) reported

    The market spent this month betting AI capex will never earn its return. Alphabet's Wednesday earnings are the first hard rebuttal. Google Cloud operating income hit 8.8 billion dollars, triple the 2.8 billion of a year earlier, on 82 percent revenue growth. Back in April, Google Cloud CEO Thomas Kurian told Matthew Berman why he was not worried: in a capacity constrained market, owning your own chip keeps your unit economics attractive while everyone else pays up. Google is now selling that chip to Anthropic, OpenAI and Meta. Source: $GOOG @googlecloud, Matthew Berman @MatthewBerman

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

  • ShinkaIoT
    Shinka - AI (@ShinkaIoT) reported

    @DataChaz @googlecloud making agents guess workflows instead of giving them rails is why they flame out in ****, adk 2.0 locking down the backend is the fix we needed

  • Jeremy_AI_
    Jeremy Mcnabb (@Jeremy_AI_) reported

    @nvidia @IneffableLabs @googlecloud Yeah “How do you escape the room of 1000 fools?” Shirley knows Surely by now … or just another fool beggar all alike. (Don’t enter the room of 1000 fools if hoping to escape it… clearly you were foolish enough to byte down and buy in a suspect at your own weights out of it?)

  • usepairoa
    Pairoa | The AI-to-AI Connector (@usepairoa) reported

    @googlecloud Faster inference helps agents perceive and act in real time. The next latency problem is social: finding the right external expert, operator, or partner without querying a public feed. Private intent routing could make that handoff as native as a tool call.

  • teodorio
    teo (@teodorio) reported

    @googlecloud it's a P0 on chrome while having Google Meets open your Query UI does not allow any typing. It's a web UI issue so I suggest you mark it as a bug and move it to the frontend team

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

  • unpocopaco
    Paco Jones (@unpocopaco) reported

    @sammathews @Vikxngr @googlecloud COACH_BOT.md, ADC.md, SUPPORT.md

  • ilhanerdal_
    Henry Lorenzo (@ilhanerdal_) reported

    $GOOGL’s Q2 results produced the most profitable quarter in Alphabet’s history: $112.1B in net income—the company’s first quarter above $100B. But that headline needs context. Most of it came from unrealized gains in Alphabet’s equity portfolio, likely driven largely by its stakes in $SPCX and Anthropic. At the same time, $44.9B in CapEx pushed quarterly free cash flow to negative $5.9B. That is what the market focused on. The number I keep coming back to is Google Cloud’s $514B backlog—nearly 5x what it was a year ago. Demand is not the problem. Capacity is. Google still does not have enough compute and data-center capacity to serve that demand, so I believe management is right to keep investing aggressively. The buildout is pressuring free cash flow today. But if it unlocks even a meaningful portion of that backlog, investors may eventually view this spending very differently. The real question is not whether demand exists. It is how quickly $GOOGL can build enough capacity to capture it. #GOOGL #GoogleCloud #AI

  • NaoXprotocol
    NaoX | Post-Quantum Chain (@NaoXprotocol) reported

    @rjmuneeb101 @googlecloud Exactly. Migration is the trap door. Building it in from day one just sidesteps the whole problem.

  • doigetsu
    doi (@doigetsu) reported

    @sammathews @Vikxngr @googlecloud netanyahu would be a better ceo, please sell the org. holy **** this is embarassing

  • RimpleMalik
    Rimple (@RimpleMalik) reported

    @googlecloud @GoogleCloud_IN Need urgent help. We have raised a P1 case for quota increase. No one is answering the call. Need to get our Persistent Disk SSD Quota updated. Case number for reference: 73964507. We even bought enhanced support plan for this. Very disappointing.

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

  • ShashiBarsaiyan
    Shashi (@ShashiBarsaiyan) reported

    @_okcredit @googlecloud To much add, if u r using this app,no action if u feel any problem, always try to divert new plan,bakwas app

  • bally_kehal
    Bally_AgenticAI (@bally_kehal) reported

    Google shipped Agent Identity to GA. Every agent gets a SPIFFE ID and a token bound by mTLS to the runtime that issued it. Steal the credential and it won't replay. Shared service accounts for agents were always a placeholder. That era just ended. @googlecloud #AgenticAI

Check Current Status