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

• 
  Valentina Valdes (@valenvp03) reported 4 minutes ago

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

• 
  Prashanth Vaidya (@thecodemarathon) reported 7 minutes ago

  @GoogleCloud_IN @googlecloud Have DMed, please include the reason why a verification failed rather than asking the customer to redo the verification blindly again and again!

• 
  Usman Bashir (@usman_basheers) reported 11 minutes ago

  @DataChaz @googlecloud The 50% token cut is nice, but the failure mode I keep hitting is agents retrying the whole workflow instead of just the failed step. Does ADK 2.0 fix that granularity, or just the guessing part?

• 
  teo (@teodorio) reported 11 minutes ago

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

• 
  Ffeennddeerr (@ffeennddeerr) reported 12 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.

• 
  Ai Trend (@Ai_Trend_) reported 14 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

• 
  Shailendra Varma (@_shailendra_var) reported 15 minutes ago

  🚨 URGENT REQUEST — Please Expedite My Project Reinstatement My Google Cloud project supporting Tailor Book has been suspended, and the entire app backend is currently down. Because of this, thousands of tailor businesses using the app are unable to manage their shops and daily work. My case has already been escalated to the internal team for project reinstatement, but the process is taking time while our users are completely dependent on the service. 🎫 Case ID: WRUOFYRHZ3ARFV4H6U2YBMRYEA @GoogleCloud @Firebase Please review my case and expedite the reinstatement process. This is a live production application, and every additional day of downtime is directly affecting real businesses. I understand that security reviews take time, but I urgently request your help in restoring the project as soon as possible. 🙏

• 
  DWE Post (@dwepost) reported 16 minutes ago

  @googleaccount Dear Google Team, I can’t access my Gmail account. I forgot my password, and the standard recovery options are not working for me. This is my primary account. Please help me recover it as soon as possible. Thank you. @googlechrome @googlecloud help me.

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

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

• 
  Viraj Kokane (@virajkokane_) reported 18 minutes ago

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

• 
  Mr. Palindrome (@bladeofshanghai) reported 22 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 ****.

• 
  Decisively Digital (@DcyDigital) reported 24 minutes ago

  @effiekav @googlecloud The moat is permissions, provenance and escalation paths, not model IQ. Most enterprises will find the bottleneck was never AI, it was that nobody could say who may do what.

• 
  Antonio Gomes (@onchainantonio) reported 24 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.

• 
  Garrett Smith (@gsmithw91) reported 24 minutes ago

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

• 
  Bernaridho Hutabarat (@bernaridho) reported 25 minutes ago

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