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:

• 
  Isabella (@aochan99_) reported 4 minutes ago

  @ixen @googlecloud You can talk to @EllaCoding, support won't help you

• 
  Ziku.eth (@yungziku) reported 5 minutes ago

  $DATA Team releasing an app Market asked -> is it useful? (Make profit for the users) -> Not sure? -> choppy pricing Team getting gold check Market asked -> How easy is it to get gold checked? -> Extensive verification? -> violent upward pivot Team partner with @googlecloud Market asked -> What is the scale of this partnership? -> Not sure -> Slight sell down “Buy the rumor, sell the news” (1/3)

• 
  Revolgy (@Revolgy) reported 6 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

• 
  Mathieu Kessler (@mayeu20) reported 7 minutes ago

  @googlecloud Embedding agents directly into network products is a strong integration.

• 
  المهندس وسام حاج محمد | AI Architect (@WessamHMuhmad) reported 11 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!"

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

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

• 
  Amrish Kumar (@_amrishkumar) reported 13 minutes ago

  @googlecloud @GoogleCloud_IN It's now one whole month and the escalation manager who was assigned last replied on May 9th requesting for 2-3 business days and I have never heard back from him

• 
  Bavin (@B4_winZ) reported 14 minutes ago

  @googlecloud @GoogleCloud_IN im getting this error : This action couldn't be completed. [OR_BACR2_44] for many times as I tried many times to upgrade my account. it was really urgent. my cards are currently unusable so I prefer GPay UPI Mandate plaease Help

• 
  Rash05 (@JobbingPsych) reported 17 minutes ago

  Stuck in support limbo with @GoogleCloud. Tried to upgrade to deploy our website, but got automated fraud-blocked. It's been 5 days since I uploaded my verification docs to Case #72047300 with zero response. Disappointing customer service. Urgent help needed! @GoogleCloudTech

• 
  NetriXD (@NetrixdO) reported 27 minutes ago

  @sammathews @googlecloud ah yes so instead of doing productive things like kicking out entire management plus dardo razork and upset that u so eagerly defend, u do AI bullshit. Great job Sam, i ******* know the org buying fnatic will be 100x better then whatever this **** is. Incompetent CEO as usual.

• 
  Evin (@evinjohnn) reported 27 minutes ago

  @GoogleCloud_IN @googlecloud Hey , Need urgent help , I have made the payments , but my api keys are still showing expired , my entire app runs on it , please look into it asap

• 
  The AI Automation Agency (@ham_basshogg) reported 29 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.

• 
  Jakob (@jakob_btc) reported 29 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.

• 
  Guilherme O'Tina (@guilhermeotina) reported 30 minutes ago

  @addyosmani @googlecloud the verification problem gets wild at this scale. a 10 minute agent fails loud, you catch it. a 10 hour agent can drift into a confident wrong answer because every individual step looked fine in isolation. the feedback horizon is the real bottleneck, not the context window

• 
  Ziku.eth (@yungziku) reported 32 minutes ago

  $DATA Team releasing an app Market asked -> is it useful? (Make profit for the users) -> Not sure? -> choppy pricing Team getting gold check Market asked -> How easy is it to get gold checked? -> Extensive verification? -> violent pivot Team partner with @googlecloud Market asked -> What is the scale of this partnership? -> Not sure -> Slight sell down “Buy the rumor, sell the news” (1/2) —— What does it means? It means when the team pull it off the repricing upward will be violent Equivalently would be a violent reprice downward if the team fail to pull off early infrastructure claims