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:

• 
  Sumeet (@sumeetweb) reported 5 minutes ago

  Update: @googlecloud outage caused this.

• 
  Andrew J. Moats (@11drawbridge) reported 6 minutes ago

  @ChiCityBrian @MLBStats @googlecloud It was down the line, so that would naturally make some home runs seem longer than they are.

• 
  Rooke Poole (@rookepoole) reported 7 minutes ago

  @googlecloud I got connected now but since this automated maybe not help me with the hackathon

• 
  Maciej Donajski (@MaciejDonajski) reported 10 minutes ago

  Is it just me or @Google and @googlecloud changed something and now I have to log in to gcloud everyday vs once every few months. Similar with oauth I have the full login flow more often than I used to. Is it some new policy or am I imagining it?

• 
  Garrett Smith (@gsmithw91) reported 11 minutes ago

  @googlecloud @ThomasOrTK What is the magic number of follow ups and requests someone has to do to get resolution for billing support? Its beyond 30 at this point.

• 
  Antonio Gomes (@onchainantonio) reported 16 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.

• 
  Aritan (@Aritan_lover) reported 17 minutes ago

  @googlecloud Dear @Google, I’ve paid a significant amount for your services and now face a serious financial issue. For more than 10 days, I’ve tried to reach a human support agent, but there is no clear way to do so. Please review this urgently and connect me with a specialist.

• 
  wiinks (@wiinksdotcom) reported 17 minutes ago

  Been part of @GoogleStartups for almost a year, have not talked to anyone from Google, can't even use the credits becuase @googlecloud compliance flagged the account - just going to remove google oAuth login.

• 
  nicholas ⛱ (@nnnnicholas) reported 20 minutes ago

  @_lopopolo @googlecloud @OpenAI woah they poached you? but you were no. 1! maybe you can tell the people responsible for gmail that gemini integration is terrible

• 
  Caffeinated Acrimony (@dick41259892) reported 21 minutes ago

  @googlecloud Pajeet ceo? No thanks. The software is for sure total ****.

• 
  ofPowerofWant (@ofPowerofWant) reported 24 minutes ago

  @googlecloud I did collect everything and attempt to do this but @X has joined team "lock you out with something you never asked for" so without a passcode it's not happening Will just have to vent frustrations each time I receive an email until we can't access this at all either

• 
  Isabella (@aochan99_) reported 27 minutes ago

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

• 
  Scarab (@ScarabOfficial) reported 29 minutes ago

  Hey, #Google, You still haven't corrected the poor English in your #GoogleCloud ad'. How many more times do I have to tell you ?

• 
  atul joshi (@ajoshi31) reported 32 minutes ago

  @GoogleCloud @GoogleCloud_IN @googleclod It's disappointing to see a startup application stuck for weeks with no ownership. Since June 12, every follow-up has resulted in the same response: "please wait 2 business days." No ETA. No decision. No accountability. I've already delayed our infrastructure rollout because of this. If there's still no resolution by this week, we'll migrate to other provider. Timeline: • June 12: Application submitted • Multiple follow-ups over 3+ weeks • Repeated "wait 2 business days" • Support apologized for the delays • Call scheduled, but no follow-up afterward

• 
  Brad Bonin (@cisco_brad) reported 33 minutes ago

  @googlecloud @Gartner_inc Nice recognition. The AI infrastructure space is heating up - execution matters most right now though. Curious how the actual customer deployments play out over the next year or two.