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:

• 
  Sohail Shaikh (@SohailS90974443) reported 33 seconds ago

  @fameforecasts @googlecloud I also had this same issue a week ago it’s fustrating because their appeal is junk but I did get mine back tho via technical support. Need help?

• 
  Brian Smith (@sirwart) reported 1 minute ago

  @googlecloud I'm trying to enable the Compute API but it continually fails. I can't open a support ticket without paying. That requires me to be a "Support Account Admin" of my org. Trying to add that perm to my account also fails. Could you please help?

• 
  Pestilent Worm (Fired everyone) (@Rude_Jenkins) reported 3 minutes ago

  @googlecloud **** YOU GET RID OF THE **** MLB TV AD

• 
  lil_mosey_total_rockstar 🎸 (@TotalLil_m0sey) reported 6 minutes ago

  @googlecloud vertex api is so *** compared to open ai api its not even close i ******* hate using vertex api and ur documentation sucks

• 
  Neeraj Dhiman (@imInforian) reported 7 minutes ago

  @GoogleWorkspace @googlecloud @googledevs This kind of experience erodes trust more than the bug itself. Because the issue isn’t just technical anymore — it’s systemic. 10/n

• 
  Self Protocol (@SelfProtocol) reported 7 minutes ago

  ERC-8004 gives AI agents a portable onchain identity, the critical starting point for agent-to-agent trust. But there's a gap. When an agent borrows funds, claims a yield boost, or votes in governance, the protocol has no way to know if a real human authorized it, or if it's a bot farming rewards across hundreds of wallets. ERC-8004 gives agents an identity. It doesn't verify the human behind them. That's where Self fits. Through ZK proofs, Self anchors an agent's onchain registration to a verified human, without ever exposing their personal data. The ZK proofs map directly into ERC-8004's Validation Registry hooks. Protocols can check that an agent's operator is OFAC-compliant, or above a required age, all from existing Self infrastructure. This isn't theoretical. → @aave integrated Self's ZK proof-of-humanity to offer verified humans boosted yield on USDT and WETH, a direct financial incentive for human verification in a DeFi environment increasingly populated by autonomous actors. → @googlecloud integrated Self into its Web3 Testnet Faucets to ensure real humans get 10x more @Celo Sepolia testnet tokens, verified through ZK proof-of-humanity, no personal data required. Both cases are the exact problem ERC-8004 surfaces, already live and in production. The agentic web needs both layers. The agent identity standard and the verified human behind it. The full breakdown of how they work together is in the blog 👇

• 
  olifog (@fogelin) reported 10 minutes ago

  @andy_pavlo @googlecloud @CMUDB never felt more jealousy for an undergrad course

• 
  faizan khan (@faizan10114) reported 16 minutes ago

  A user dropped out of our docs into the AI chat, asked a question, got the wrong answer, and left bad feedback. Before this, that kind of issue would have turned into guesswork. This time I used @PostHog to trace the user path, @googlecloud to pull the production logs, and direct database access to rebuild the exact chat session. That made the bug obvious: the app had the right customer data, but the chat pipeline was not grounding the model with it correctly. I fixed the chat flow, added better Cloud Run + PostHog observability, and now we can see where users come in, where they fail, and why.

• 
  Any AI (@AnyAI_in) reported 16 minutes ago

  @cgtwts Link budgets to Pub/Sub topics to trigger scripts or Cloud Functions that disable billing, revoke keys, or shut down resources when thresholds are hit. If spend exceeds 200% of normal, automatically disable the project. @googlecloud must have a pre-paid option, like OpenAI API.

• 
  Jared K (@TheSilverHorsey) reported 16 minutes ago

  @googledevs @googlecloud help me out here guys. I really want to use Vertex for my project, but you are NOT making it easy.

• 
  Michael Teka (@z3vios) reported 23 minutes ago

  It might take months to attain compentency in @GoogleCloud, but it will be worth it aye. But not in a dime-a-dozen, garbage outputs kinda way. I been programming before a lot of you were a twinkle in your Father's eye you see. People walk away with value, after encountering me. I listen for a while, and output useful information. My programs solve problems, automate and enhance workflows. No fluff, just the facts. Revenue. Sales. Hold up while I choose one build and go for it.

• 
  merkury T 060 (@TimMerk391225) reported 24 minutes ago from Sheridan Park, Washington

  @Humana @GoogleHealth @googlecloud Humana benefits card is a piece of **** this year!!!! this is my 3rd year. I went to Fred Meyer East Bremerton, WA. I purchased Bottled TEA. the Humana Benefit Card 2026 rejected my purchase?? I've purchased the same bottle for 3 years with the same card!!!

• 
  Cihat Kaya (@cihatkaya) reported 24 minutes ago

  @googlecloud While the taxonomy is helpful, I find the lines blurring more rapidly than these definitions suggest. The "learning capabilities" of a well-trained bot can often mimic an agent's autonomy, especially within a narrow domain. Where do you draw the practical distinction for an end-user who just wants a problem solved?

• 
  Agireon (@agireon) reported 28 minutes ago

  @googlecloud @wiz_io Multicloud security just became Google's problem to solve at scale.

• 
  Cel Quintero 𝕏 (@Cel_Metal_) reported 29 minutes ago

  Key was live when reported → patched after my submission. Resubmitted with full PoCs → closed as Not Applicable because it no longer reproduced. No credit, no Informative, no bounty. Low signal blocks everything. @GoogleCloudSec @googlecloud @Bugcrowd #bugbounty #infosec