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:

• 
  Orvyl Tumaneng (@orvylft) reported 42 seconds ago

  @googlecloud @gcpcloud URGENT: Project on1-271405 — billing was suspended ~30-60 days ago, now restored and paid. Compute Engine instance and persistent disk are gone. Production database data at risk. Please help recover before final deletion. #GCPSupport

• 
  Garrett Smith (@gsmithw91) reported 57 seconds 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.

• 
  S.A (@A_Sabo8198) reported 3 minutes ago

  @nvidia @googlecloud Cerebra’s goes up 20$ Nvidia down 2$😱😑😑 Release the beast Jensen! Enough is enough!! Everyone else got rich😑😴 wake up! Buy the shares back! Let’s go!🤪🧐🥸

• 
  Azy (@therealazy) reported 3 minutes ago

  @googlecloud I've had a support ticket open for a week now trying to increase the quote of projects I can add to a Billing profile. What is this non sense....

• 
  Garrett Smith (@gsmithw91) reported 6 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.

• 
  Celso Pinto (@cpinto) reported 9 minutes ago

  @bradgessler @Azure @googlecloud Yeah it’s been broken for at least a month now

• 
  Confideleap Partners Communication (@confideleapnews) reported 10 minutes ago

  @nvidia @googlecloud strong example of how innovation and trust can evolve together to support the next generation of AI-powered services.

• 
  Ricard Gardella (@RicardGardella) reported 11 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? 👇

• 
  Accademica (@AccademicaIO) reported 11 minutes ago

  @googlecloud Our organization is also a member of "Premium Assistance" and we hope we can fix this issue fast

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

  @googlecloud @lovart_ai 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!

• 
  Shayan Mashatian (@shayanrm) reported 17 minutes ago

  @_oliveiradanilo @googlecloud At minimum, they must make spikes in cost or usage notifications a default. Until they don’t do that, there is a huge risk in using Google Cloud for anything, even a simple database set up on Firebase. Specifically with so many vibe-coders and AI assistants everyone is using. AI coders have a tendency to suppress errors, and create fallbacks. They can easily create a circuit, go unseen for days and account owners end up with $$$$$$$ bills.

• 
  Brad Gessler (@bradgessler) reported 18 minutes ago

  A big reason is because you can’t sign up for half of the hyperscalers. Today I tried to open an @Azure account today & the anti-bot mechanism was broken. I then tried @googlecloud & adding an address to billing was broken. They just don’t care anymore. 🤷

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

• 
  Revolgy (@Revolgy) reported 20 minutes ago

  Open your IAM page. Count how many people have Owner access on a production project. Now ask how many of them still need it. Most teams can't answer that. Roles get granted during a migration, an incident, or because someone asked on Slack and it was faster to say yes. They never get revoked. Three years later, a developer who left is still in the system. A contractor has Editor access on a project they finished in Q4. A test account from an old integration has permissions nobody remembers approving. This isn't malicious. It's drift. But drift is how breaches happen — and how audits fail. When a DORA or SOC 2 review arrives and you have no access history, no continuous compliance log, and no clear answer for who can do what, the gap between "we thought we were fine" and "we have a problem" closes very fast. Identity isn't a one-time setup. It's a maintenance task that nobody assigns. Solve security. With Revolgy. @googlecloud #GoogleCloud #IAM #IdentitySprawl

• 
  Luca 🦖 | #fncforever | 🍉 (@sinister_in) reported 22 minutes ago

  @sammathews @googlecloud The worst possible time line