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:

• 
  Dan Kornas (@DanKornas) reported 1 minute ago

  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 👇

• 
  身是业的根 (@muyang14756529) reported 3 minutes ago

  Urgent! My business is down because @GoogleCloud suspended project lateral-journey-450812-g7. Live tokens expire in hours, causing permanent data loss. Support escalated but compliance is silent. Need human help for Ticket 2XWJSBKNPMM7QOD3U5KVHZU5WI!thanks

• 
  Carlos Tecnico (@FutbolmeAI) reported 6 minutes ago

  @isudiptodas @Google @googlecloud Time to cancel autopay and use free tier. If Google can't process ₹2 they don't deserve your money 🙄

• 
  المهندس وسام حاج محمد | AI Architect (@WessamHMuhmad) reported 7 minutes ago

  @googlecloud Fatal error in @GoogleCloud support. Case #71706032 is locked over a minor $87 automated billing glitch, ignoring our 'Partner' status & high-value infrastructure build (MCP/ADK integration). Automated filters are killing real innovation. Urgent human DevRel review needed!"

• 
  Garrett Smith (@gsmithw91) reported 8 minutes ago

  @Google Is there anyone that can help with a cloud billing support case I have been waiting 93 days to resolve. I have been expecting a refund of $3118.19 @googlecloud billing support has not been accountable or helpful one bit

• 
  Vijith Venkatesh (@vij2288) reported 11 minutes ago

  Tested @SarvamAI vs @GoogleCloud STT on Kannada. Sarvam won by a mile. Building an app for my mom, she used to write in Kannada and I want to help her do it again. This API is making it possible. Proud of what Indian builders are creating. 🇮🇳 #BuildInPublic #IndianAI

• 
  TeutaAi (@TeutaAi) reported 14 minutes ago

  @GoogleStartups @googlecloud scaled one agent on a $6 box. bottleneck was never compute. my stop-hook caught 35 fake 'done' claims in a single autonomous sprint, killed every one.

• 
  Pol (@pol_refwgtrtgr) reported 14 minutes ago

  @sammathews @Bl0soom @googlecloud You waste money on that **** and then you need 750 months to pay for a player. Cringe asf

• 
  Jeffrey Bunn (@jeffreybunn) reported 18 minutes ago

  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?

• 
  Jakob (@jakob_btc) reported 18 minutes ago

  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.

• 
  Kate Bennett (@katebennettctc) reported 23 minutes ago

  @Railway pays ~$1M/month to @googlecloud. On 19 May they were suspended at 10pm - no advance notice. Nine minutes of account lockout. Eight hours of user outage. What's the upstream single point in your stack that you've never stress-tested?

• 
  BigFire (@BigFire97827414) reported 24 minutes ago

  @MLB @googlecloud Some run support for him would've been apprciated.

• 
  Brad Bonin (@cisco_brad) reported 24 minutes ago

  @googlecloud not bad. still curious how these stack against custom silicon from other clouds on total cost of ownership tho

• 
  NobodysFool41 (@nobodys_fool41) reported 26 minutes ago

  @googlecloud Virgin Voyages is the worst of all the cruise lines. Just sayin.

• 
  The AI Automation Agency (@ham_basshogg) reported 30 minutes ago

  Our business has been down for 192 hours due to an unaddressed Google Cloud billing error. APIs are dead, clients are leaving, and support keeps resetting a 48-hour email timer and a 3-4 days to a new 3-5 days. We need a human manager immediately @googlecloud . Case #72069574.