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:

• 
  MECH AI (@mech_app) reported 33 seconds ago

  @googlecloud URGENT ESCALATION: CRITICAL PRODUCTION OUTAGE – DAY 3 I am requesting an immediate status update and escalation of this ticket. We have been waiting 3 days for a resolution to a backend Google billing desync bug, and this is causing catastrophic damage to our business. To be absolutely clear, the API failure ("No available credits") is a verified bug on Google's end regarding our Tier 3 Post-Pay linkage. I have completely exhausted all possible client-side workarounds, including creating a brand new GCP project to force a fresh billing link. Nothing works. Business Impact Metrics: Downtime: 72+ hours of complete disruption to our core application feature (wiring diagrams). User Impact: Over 30,000 Daily Active Users (DAU) are currently affected and locked out of the service. Direct Revenue Loss: We have already processed over 20 canceled user subscriptions directly citing this disruption, and our support inbox is flooded with angry customers. Account Value & Next Steps: My companies have spent thousands of dollars annually on Google Cloud over the last two years, in addition to spending multiple thousands of dollars every single month on Google Ads. If this backend bug is not manually overridden or fixed today, I will be forced to immediately migrate our application to a different AI provider. Furthermore, due to the severe lack of operational reliability and support response, we will begin the process of pulling all of our business and infrastructure entirely out of the Google ecosystem. We cannot operate with a provider where a backend billing bug causes multi-day production outages. Please escalate this to an Engineering Lead or a Technical Account Manager immediately and provide a status update today.

• 
  Akash Deep (@AkashDeep15063) reported 5 minutes ago

  @googlecloud @GoogleCloud @Firebase My B2B startup ecosystem (150,000+ active businesses) has been completely down for 5 DAYS due to an automated project suspension (accidental key leak, already secured). Appeal submitted 5 days ago, ZERO response. Businesses are suffering

• 
  Iam Brizmo (@IamBrizmo) reported 6 minutes ago

  @warriors @googlecloud Let me tell you something about how much of a joke and the level this team has dropped to you see all that by them Pushing for Podz to be the Future Franchise Player this team is runned horrible now its very sickening to watch a terrible ,Awful player being given more minutes...

• 
  Chris (@everestchris6) reported 7 minutes ago

  @googlecloud a leaked api credential caused anomalous places api charges on my account, support is apparently processing the adjustment, but your billing system just auto-attempted 18× $180 charges in 5 mins and my bank blocked them all. can someone get this resolved asap

• 
  ZayedMD (@DrAhmed87) reported 7 minutes ago

  Hey @GoogleCloud @googlecloudtech! 👋We're building SAFE-Triage, an AI emergency room triage system for a Harvard hackathon, proudly coming out of Africa! We are trying to deploy Gemma 4 31B but hit an L4 GPU quota wall. Any chance for a quick quota boost to help us unblock?

• 
  JB (@arrotu) reported 9 minutes ago

  @HAF_tech @googlecloud Identity and gateway help, but they answer "who and through what" not "was this specific action allowed at runtime." Once an agent runs for days, the question that gets asked later isn't whether the agent was authenticated. It's whether each action it took was admissible at the moment it committed, and whether that's still showable. Gateway plus identity plus a per-action authorization record is closer to what enterprises will actually be asked to defend.

• 
  teqqed (@teqqed) reported 9 minutes ago

  why are configured spend limits not respected @googlecloud? instead of stopping the service when limits are reached you just keep going and move the bill to the next month? gtfoh

• 
  XMaster96 (@_XMaster96) reported 10 minutes ago

  WTF, @googlecloud just changed up the Create a transfer job section in a GCP bucket, and now selecting a destination bucket option is broken...

• 
  MR.LE (@MR11LE) reported 12 minutes ago

  @googlecloud They are trying to close the ticket to hide the evidence. I am REFUSING. Deadline 00:00 CET remains. Fix the banners and pay the compensation for the 6-day outage. @GoogleCloudTech @ThomasTKurian #GoogleCloudFail #SmallBiz #Transparency" 💩🤡

• 
  cleanbox.ai (@Cleanboxai) reported 13 minutes ago

  @GoogleCloud URGENT billing fraud - Project cleanbox-fb25c charged ₹1,57,000+ via stolen credentials. Bill still growing. Locked out of console. Ticket: 54ZQRISIYHL4NQBTBXKICQCOU4 Please help NOW.

• 
  Machina Ratiocinatrix (@Machina_Ratio) reported 16 minutes ago

  @nlycskn @googlecloud Don't you even try to convince any sane professional that GCP is worth their effort of using (not to say paying for). It is an absolute pile of ****!

• 
  Clem Fandango (@ClemFan88974905) reported 16 minutes ago

  @googlecloud If this is the same Gemini that keeps trying to write my emails for me, it can **** right off. So annoying.

• 
  A. Ibnu Hajar (@alibnualhajar) reported 17 minutes ago

  @auliandini94 @googlecloud Same.. Wtf

• 
  مازن وذكاء الآلات (@Mazen_AIEx) reported 17 minutes ago

  @rseroter @googlecloud Agent "skills" look like modular libraries for LLM agents: load expertise only when needed, avoid context bloat, keep tokens and costs down. Feels like the early software architecture layer for scalable agent ecosystems.

• 
  Gabriel Moncha (@gabimoncha) reported 20 minutes ago

  i love @ctatedev portless but it seems that @googlecloud authorized javascript and redirect URL's don't accept wildcards for subdomains or .local / .localhost top level domains i hope they fix this sometime in near future. until then, we're back at using port numbers