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
Florence, SC 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:

  • CJ46724511
    CJ🇺🇸✝️✡️☪️ (@CJ46724511) reported

    @MLB @googlecloud 84mph lollipop down the center of the ****** pipe. Lol

  • Revolgy
    Revolgy (@Revolgy) reported

    Nothing changed. That's the problem. An idle environment nobody noticed running for six months. A staging server promoted to **** and forgotten. A license for a person who left the company in February. A BigQuery job running every hour. Nobody knows why. Finance asks why costs went up. Engineering says nothing changed. Both are right. The bill isn't lying. You just can't see what's inside it. Cutting the number is the easy part once you know what you're actually running. Most teams don't know. They find out when the invoice arrives and work backwards from there. We build visibility first. Cost follows. Solve cost. With Revolgy. @googlecloud #GoogleCloud #Revolgy #ManagedServices

  • bernaridho
    Bernaridho Hutabarat (@bernaridho) reported

    @googlecloud What more do you need? I'm tired of giving repeatedly same information, and Google did not solve it. Are you the customer center staffs are just reshuffled too often?

  • CalebMccombs2
    Caleb Mccombs (@CalebMccombs2) reported

    @googlecloud @googlecloud @GoogleCloudTech Our S-Corp is actively processing enterprise AI workloads on Vertex, but we've been ignored by the Startup Program support queue for over a week (Case #00284484). Who handles escalations? We are evaluating our Azure options if we can't get unblocked.

  • 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

  • strategem360
    Strategem360 (@strategem360) reported

    Google Cloud outage hits India: Fire in a third-party data center triggered full shutdown. Services disrupted for users across the region. Google investigating and working on failover. #GoogleCloud #CloudOutage

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

  • RicardGardella
    Ricard Gardella (@RicardGardella) reported

    Fixed a sneaky Terraform @HashiCorp @googlecloud bug in Magic Modules: @GoogleCloudTech Problem: Setting enable_proxy_protocol = false after it was true didn't send the update to the GCP API properly. What was wrong? 👇

  • 63green
    63green (@63green) reported

    The spam phone calls and emails from @googlecloud sales people automatically disqualifies them from consideration. Same reason I refuse to use @Cloudflare. If the quality and reputation of your product doesn’t speak for you, **** off, don’t call or email, I’m not interested.

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

  • ham_basshogg
    The AI Automation Agency (@ham_basshogg) reported

    @googlecloud Well that was an attempt to take me off X and offer zero assistance. I will post my customer support chats with @AskGoogleCloud support chats so people can see what I’ve experienced. I will be out of a job next week because of @googlecloud

  • DanKornas
    Dan Kornas (@DanKornas) reported

    I used Codex to build a small bug-reporting voice agent with @AssemblyAI's Voice Agent API. The demo was simple: A FastAPI service is down in Google Cloud. The agent has to collect the incident details by voice and turn them into a useful report. It asked for: • affected service • exact error message • user impact • severity • suggested next action By the end, it had the core ticket: @FastAPI service in @googlecloud is down for the whole company. Error: "no service found." Severity: critical. Engineers should reproduce locally and investigate. That is where voice agents start to make sense to me. Not as a flashy chat demo. As a way to capture messy operational details while someone is talking. AssemblyAI handles the voice loop: audio in, audio back, turn detection, and tool calls with JSON Schema. This was still a quick Codex-built CLI demo. I would harden the prompts and test edge cases before putting it near production. But the first working version came together fast. Try the live demo in the reply 👇

  • kylecordes
    Kyle Cordes (@kylecordes) reported

    @VeryWellVersed @googlecloud There's a reasonable chance this never gets corrected and tallied to fraud and instead results in loss of your account. My advice is to step off social media and stay up all night moving every account, etc. that matters to an email address that won't be affected if it happens.

  • _eosike
    D!kstra_Algo (@_eosike) reported

    @lxmwaniky @TtnlxMubz @googlecloud You'll never get any valuable Certification for free, you'll have to spend a good time studying and the examination fee. Exam is proctored, you can do it from anywhere as long as you’ve steady Internet.

  • jeffreybunn
    Jeffrey Bunn (@jeffreybunn) reported

    Ask: our @googlecloud project was charged ~$1.3k after ~5.6K unauthorized calls in a few hours to Gemini image models we don’t use. Support credited ~$660, but we’re still stuck with the rest. Looks like legacy API access may have been abused. Anyone at GCP able to review?

Check Current Status