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:

• 
  VLAD ARBATOV (@vladzima) reported 10 minutes ago

  @arseniycodes @googlecloud it would be very cool to support RN

• 
  zbt3sup (@zbt3sup1) reported 10 minutes ago

  @intel @googlecloud Bad choice for your engineers

• 
  Bally_AgenticAI (@bally_kehal) reported 12 minutes ago

  Google's Agent Identity gives each agent a SPIFFE ID and a token bound by mTLS to the runtime that issued it. Steal the credential and it won't replay anywhere else. Shared service accounts for agents were always a placeholder. @googlecloud #AgenticAI #IAM

• 
  Mariz (@MarizMelo) reported 13 minutes ago

  @googlecloud forcing users into prepaid sucks. Maybe time to look for alternatives to host your #AI product :/

• 
  Numero Uno🇳🇬 (@John_dgreatestt) reported 15 minutes ago

  @Concordium @Google @googlecloud Runtime identity solves a crucial enterprise security problem

• 
  Rimple (@RimpleMalik) reported 18 minutes ago

  @googlecloud @GoogleCloud_IN Need urgent help. We have raised a P1 case for quota increase. No one is answering the call. Need to get our Persistent Disk SSD Quota updated. Case number for reference: 73964507. We even bought enhanced support plan for this. Very disappointing.

• 
  KleurigDrieluik (@KleurigD) reported 20 minutes ago

  @GooglePlayBiz he Google play, why is Developer Support ignoring support questions with detailed technical analysis from @googlecloud Gemini and @Firebase support?

• 
  Conrad Lotz (@conradlotz) reported 22 minutes ago

  BREAKING: Google Cloud Hands AI Agents Full Cloud Cheat Sheet Thread 1/3 Google just made BigQuery, Cloud Run, and Kubernetes natively usable for Claude Code, Cursor, and Copilot agents. One command integration. Free tier available. Thread 2/3 This means your AI coding agents can now properly orchestrate real cloud resources without constant prompt engineering around APIs. Thread 3/3 Huge for production builders moving agents from prototypes to deployed services. Test it on a small workload first. #AI #GoogleCloud Bridges the gap between AI coding assistants and real infrastructure management; accelerates agent adoption. What cloud service do you want AI agents to handle first?

• 
  Christian Nonis (@christiannonis) reported 24 minutes ago

  I am (unfortunately) dealing with @googlecloud and @awscloud and what I am noticing is that in months they are unable so solve any kind of problem, it’s like being bounced back by ai replies that are sold like assistance from humans, saying that they are “working on that” but nothing changes in months and also replies are all the same.. idk if they are experiencing a shortage in human labor or what’s going on but the experience has become worse than ever

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

  @googlecloud The Trust & Safety team is completely cold & irresponsible. They just sent a generic 48-72hr weekend template while knowing my countdown is in HOURS. Absolute zero empathy for small businesses. Help Ticket 2XWJSBKNPMM7QOD3U5KVHZU5WI! #GoogleCloud @GoogleCloud (2/2)

• 
  Kat MacSpyro (@KatSpyroMacD) reported 30 minutes ago

  @googlecloud Unless you can #BringValkoBack I don't care. Your product can't help me in any way, shape, or form to fulfill my wants and/or needs.

• 
  Antonio Gomes (@onchainantonio) reported 30 minutes ago

  @Googlecloud's recent post-quantum roadmap highlights just how complex this migration is. The most honest line in it is about hardware. Google says some physical replacement cycles will run past 2029. This is a company that owns its data centres, its silicon, its browser and its certificate authority. And it still cannot promise the hardware layer is done by the end of the decade. That is the whole migration in one sentence. Post-quantum is a systems programme, not an algorithm swap. Three things in the roadmap that make the point: → Key exchange was the easy part. Hybrid ML-KEM is already live on Google's endpoints. Encryption in transit moves fast because it only needs two parties to agree. → Signatures are the hard part. ML-DSA and SLH-DSA are too large for the existing WebPKI to carry, so Google is testing Merkle Tree Certificates with Chrome and Cloudflare. They did not swap the signature. They redesigned how trust is distributed. → Roots of trust are the slow part. Caliptra, TPM 2.0, OpenTitan for quantum-secure boot. Silicon has a shipping cycle. No software update shortens it. Now remove Google's advantages. No single owner of the stack. No control over the clients. Keys and signatures published permanently the day they were made. That is what a decentralised network is migrating from. It is why "we'll upgrade later" is a much bigger claim there than it sounds. The organisations with the most control are being the most careful about the timeline. Worth sitting with.

• 
  Queanbea333 (@trabea333) reported 31 minutes ago

  @googlecloud Just what no one needed or asked for. @google please don't release millions of mosquitoes onto the planet. We don't trust you. If you want to help the environment simply stop building data centers.

• 
  doi (@doigetsu) reported 32 minutes ago

  @sammathews @Vikxngr @googlecloud netanyahu would be a better ceo, please sell the org. holy **** this is embarassing

• 
  Bernaridho Hutabarat (@bernaridho) reported 33 minutes ago

  @googlecloud What more do you need? I'm tired of giving repeatedly same information, and Google did not solve it. Are you the customer center staffs are just reshuffled too often?