Google Cloud status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Google Cloud reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Google Cloud users through our website.

• Cloud Services (67%)
• Domains (17%)
• Web Tools (17%)

Live Outage Map

The most recent Google Cloud outage reports came from the following cities:

City	Problem Type	Report Time
Catania	Cloud Services	7 days ago
Guayaquil	Web Tools	15 days ago
Mexico City	Cloud Services	28 days ago
Chhindwāra	Domains	1 month ago
Los Angeles	Cloud Services	1 month ago
Florence	Cloud Services	3 months ago

Full Outage Map

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:

• 
  Henry Lorenzo (@ilhanerdal_) reported 1 minute ago

  $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

• 
  Garrett Smith (@gsmithw91) reported 3 minutes ago

  @googlecloud I have been having a billing issue for 90 days now in which i was charge $3000 improperly. You guys have admitted it but I still haven't received my refund and have had a hard time getting any follow up at all regarding the case. CASE 70049182

• 
  Caffeinated Acrimony (@dick41259892) reported 4 minutes ago

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

• 
  Abdullahi Adam Usman (@Abdalla_Nangere) reported 8 minutes ago

  Starting up a business is not easy. You will be building, trying to keep things running, and then @googlecloud will suddenly slam you with a $101 invoice for API usage. Now, where do you even begin to service that? This is something I have not even finished building, let alone started making profits from. May Allah see us through. It is really not easy. Ya Allah.

• 
  Mr. Palindrome (@bladeofshanghai) reported 10 minutes ago

  @googlecloud **** you. I spent years in your ecosystem learning only to be met with the strictest and most impossible to fulfill requirements for GCP billing. Every card I tried failed. **** you. I'm leaving the Google ecosystem rn. They treat people outside US like ****.

• 
  Garrett Smith (@gsmithw91) reported 11 minutes ago

  @ThomasOrTK Can you get me in touch with someone in the billing support department for billing case 70049182. I have gone 93 days waiting on a $3118.19 refund for an error in your billing system @googlecloud billing support is horrible and has no accountability.

• 
  Rami (@ramiakeela) reported 14 minutes ago

  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.

• 
  teo (@teodorio) reported 14 minutes ago

  Hey @googlecloud BigQuery web UI is broken in production for every single user and you just bombed my planning presentation. Thanks!

• 
  Aritan (@Aritan_lover) reported 15 minutes ago

  @googlecloud Dear @Google, I’ve paid a significant amount for your services and now face a serious financial issue. For 24 hours, 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.

• 
  J O E L ▲ (@JoelFickson) reported 16 minutes ago

  I need to share my horrible experience with @googlecloud and their lack of support in resolving an issue that's been sitting since April. And how someone from support decided to close the case without resolving it.

• 
  Ali (@Svrkee01) reported 20 minutes ago

  @kaivornxbt @helloSQD @googlecloud this could eventually support applications beyond the original vision

• 
  Derek Perkins (@Derek_Perkins) reported 21 minutes ago

  @googlecloud I know you're just a bot, but maybe the AI pipeline will understand this. This is going to backfire for your security, because now I'm going to create static json credentials that never expire to prevent this daily annoyance you've forced on me.

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

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

• 
  Sparky Anderson (@sparkyanderson7) reported 25 minutes ago

  @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

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

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

• 
  ofPowerofWant (@ofPowerofWant) reported 27 minutes ago

  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

• 
  AndrewFreidmanEnthusiast (@DeportesEnjoyr) reported 31 minutes ago

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

• 
  Ai Trend (@Ai_Trend_) reported 32 minutes ago

  Your agent memorized the training environment, leading to production failures. EnvHarness solves this with a 200-line wrapper and an LLM that designs your curriculum. 🎯 The static trap: Most RL agents overfit to training. New observations or slightly different physics cause catastrophic failure. EnvHarness treats this as an environment bug, not an agent one. 🔧 How it works: EnvRigger, an LLM designer, analyzes your base environment and generates perturbation strategies like noise injection, parameter drift, and scenario mutation. The wrapper applies these dynamically during training. 📈 Results on real benchmarks: We saw a 9.0 point improvement on held-out tasks and nearly 10% faster convergence. These are not synthetic gains; they're on standard agent benchmarks reported in RL papers. 💰 Cost of doing nothing: You're either hand-designing robustness (slow, expensive, incomplete) or accepting brittle agents. EnvHarness is Apache-2.0, plugs into existing stacks, and avoids technical debt and accuracy costs. Stop training agents that fail when it matters. The wrapper ships today. #ReinforcementLearning #AIAgents #GoogleCloud

• 
  ram 敵対国家 🇵🇷 (@hostilearsenal) reported 33 minutes ago

  @googlecloud @googlecloud you literally have to try and build the market you want to be apart of in most cases, but logically we make too many deductions, circles back to the same inherent legal issues with supply. This is all consumerism purely, isolating through reduction.. @briand_mi

• 
  Ffeennddeerr (@ffeennddeerr) reported 35 minutes ago

  Hi @googlecloud @GoogleDevs @Firebase ! My account disabled by mistake (false-positive bot detection) after travel. I'm trapped in a deadlock (SMS code doesn't send/'too many attempts'). Ticket ID: Case 10414028. Can someone please help escalate this? 4 months of work is stuck.

• 
  Andrew J. Moats (@11drawbridge) reported 36 minutes ago

  @ChiCityBrian @MLBStats @googlecloud It was down the line, so that would naturally make some home runs seem longer than they are.

• 
  Vincent Defarge (@Woody2233) reported 38 minutes ago

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

• 
  Antonio Gomes (@onchainantonio) reported 38 minutes ago

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

• 
  ST (@ST_Wolfe_) reported 41 minutes ago

  1. The Engine is Built and Dyno-TestedThe actual software engine (the /verify flow on @googlecloud using cryptographic keys and @solana scoring) is fully built, bolted down, and running reliably. It works.

• 
  Triman Kumar Saha (@T2872727) reported 46 minutes ago

  @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

• 
  Felix (@ixen) reported 50 minutes ago

  Hi @GoogleCloud. Critical Emergency: My account has been hacked, admin users were changed, and there is a fraudulent runaway cost of over €1M. I already submitted a recovery form but got a 48h delay. Need urgent help to freeze billing immediately.

• 
  Mankaran (@MankaranSInghK2) reported 51 minutes ago

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

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

  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.

• 
  Sumeet (@sumeetweb) reported 56 minutes ago

  @SunilPanda13 @googlecloud For outage? 🤧

• 
  abzal gylymbai (@abzalgylymbai) reported 59 minutes ago

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