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:

• 
  Howard Beale (@Mad_as_Hel) reported 1 minute ago

  @googlecloud Good, because they need help !

• 
  luba luft (@luba_loop) reported 4 minutes ago

  been migrating my company onto a new @googlecloud GCP Org this week and it's a terrible experience. Been blocked since Monday due to quota limits and it is IMPOSSIBLE to get in touch with a human about it. I am trying to give you tens of thousands of dollars, help me do it!!!!!!!

• 
  EDJ (@edj_FL) reported 4 minutes ago

  @MLB @googlecloud @CleGuardians Too bad the Guardians offense is absolutely atrocious

• 
  saurav (@5auravv) reported 4 minutes ago

  I need urgent help from a real human at Google Cloud Billing / Google Payments team Between 14 May and 29 May 2026, my ICICI Bank account was debited 103 times via UPI AutoPay to Google Cloud. @GoogleCloud @GooglePayIndia @Google_India_

• 
  rahul gupta (@guptarahul07) reported 5 minutes ago

  Hi @GoogleCloud_IN @googlecloud, I submitted a quota increase request for My Business API (Case ID: 3-9628000041428) on June 02. Not able find or track this case ID. Can you help check the status?

• 
  PBAT in my Veins (@thatjosephodeh) reported 7 minutes ago

  Spent the last 24h stuck in a brutal deployment loop trying to launch n8n on @GoogleCloud Run + Cloud SQL. For a mid/senior dev, the fragmentation & complete lack of ecosystem integration is a massive failure. Here is a breakdown of why GCP feels broken right now. 🧵👇

• 
  Dan Kornas (@DanKornas) reported 11 minutes 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 👇

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

• 
  Prashanth Vaidya (@thecodemarathon) reported 19 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!

• 
  Adam McG (@hulkintosh) reported 24 minutes ago

  @googlecloud I have to put up with this **** at work. Just show me the excel document with all of the features. Your “Google Sheets” stuff is garbage.

• 
  Shayan Mashatian (@shayanrm) reported 24 minutes ago

  @_oliveiradanilo There are more and more reports of unexpected builling issues with @googlecloud. We had our own share of unexpected charges - more than once - and there is always an explanation by them somewhere that why it is your mistake. You could do x to know and avoid it (a policy or features buried under a million pages and options to know about), there is a line somewhere in terms of use, etc. Practicllay, you need to keep the billing page open and refresh every few hours to make you won’t go bankrupt. They need to revisit the whole issue, it’s becoming very scary to utilize their services.

• 
  Revolgy (@Revolgy) reported 25 minutes ago

  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

• 
  Danilo Oliveira (@_oliveiradanilo) reported 25 minutes ago

  @shayanrm @googlecloud yeah, the gemini are passing our quality tests. the inference speed and quality are nice. It is working to our problems. they need improve the billing aspect and the deprecation policy. We need every month update the models and redo the tests.

• 
  Danilo Oliveira (@_oliveiradanilo) reported 26 minutes ago

  @shayanrm @googlecloud I think that the big issue with gemini is related with conway law. The need iterate fast, but they are chained with gcp platform.

• 
  Ricard Gardella (@RicardGardella) reported 28 minutes ago

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