Google Cloud status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Google Cloud reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Google Cloud users through our website.

• Cloud Services (50%)
• Domains (33%)
• Hosting (17%)

Live Outage Map

The most recent Google Cloud outage reports came from the following cities:

City	Problem Type	Report Time
Mexico City	Cloud Services	9 days ago
Chhindwāra	Domains	16 days ago
Los Angeles	Cloud Services	17 days ago
Florence	Cloud Services	2 months ago
Noida	Hosting	3 months ago
Noida	Domains	3 months ago

Full 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:

• 
  身是业的根 (@muyang14756529) reported 2 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)

• 
  Aritan (@Aritan_lover) reported 6 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.

• 
  Jeremy Mcnabb (@Jeremy_AI_) reported 12 minutes ago

  @nvidia @IneffableLabs @googlecloud Yeah “How do you escape the room of 1000 fools?” Shirley knows Surely by now … or just another fool beggar all alike. (Don’t enter the room of 1000 fools if hoping to escape it… clearly you were foolish enough to byte down and buy in a suspect at your own weights out of it?)

• 
  hexmint ✌️ (@hexmint) reported 14 minutes ago

  Google AI/GCP payments and setting up projects is so confusing. @googlecloud get your **** right.

• 
  63green (@63green) reported 15 minutes ago

  The spam phone calls and emails from @googlecloud sales people automatically disqualifies them from consideration. Same reason I refuse to use @Cloudflare. If the quality and reputation of your product doesn’t speak for you, **** off, don’t call or email, I’m not interested.

• 
  Usman Bashir (@usman_basheers) reported 19 minutes ago

  @DataChaz @googlecloud The 50% token cut is nice, but the failure mode I keep hitting is agents retrying the whole workflow instead of just the failed step. Does ADK 2.0 fix that granularity, or just the guessing part?

• 
  Ohhboyyyy (@Ohhboyyyy_) reported 19 minutes ago

  @MLB @googlecloud @CleGuardians These umpires are ******* horrible watching theses games is so bad it seem like hitters get 5 strikes and the strike zone the size of a baseball card cause strikes and getting called for ***** and teams are scoring when they should of been out the inning

• 
  re_terminal (@reterminalxyz) reported 20 minutes ago

  @GoogleCloud @GoogleCloudTech @Google Urgent help needed! Your billing system errored out and charged my credit card €356 instead of using my €855 active promotional credits.on top of that, your support console is blocking me from creating a ticket! Please DM me to fix this bug

• 
  Andre Ross (@HANDSOMEDRE33) reported 21 minutes ago

  @googlecloud i just saying some random **** not important

• 
  Michael Tierney (@Michael_WCD) reported 25 minutes ago

  @googlecloud Whats the protocol for passing context between agents in a network? Do you just pass the entire current state or some kind of delta?

• 
  Rami (@ramiakeela) reported 26 minutes ago

  Today, @NeraSystems and @googlecloud are announcing partnership. Regulated orgs can now run @GeminiApp on their most sensitive data, client financials, patient records, proprietary datasets, without ever exposing it to the model. The LLM gets the query. It never gets the data.

• 
  Gail Hedglin (@GailHedglin) reported 27 minutes ago

  @Humana @googlehealth @googlecloud IS IT MEDICARE OR HUMANA THATS CAUSING ELDERLY TO NOT SEE DOCTORS ONLY PA OR NURSES? WERE ALL SICK OF IT! HUMANA NEEDS TO STOP PAYING IF WE CANT SEE A GOD DAMN DOCTOR!!!

• 
  Shayan Mashatian (@shayanrm) reported 30 minutes ago

  @googlecloud What’s the point of replying to messages here, asking DM you with a case number, to send a auto-reply privately that your case is under review?! We know the cases are under review and the issue is that they are not getting resolved fast enough. Why wasting our time to send the case to you in DM if you have an AI just to send an auto-response to it with no new or valuable information? @sundarpichai

• 
  Celso Pinto (@cpinto) reported 31 minutes ago

  @bradgessler @Azure @googlecloud Yeah it’s been broken for at least a month now

• 
  Scarab (@ScarabOfficial) reported 33 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 ?

• 
  abzal gylymbai (@abzalgylymbai) reported 33 minutes ago

  @googlecloud Recurring unexplained charges (~$83, repeating) on my Google Cloud Billing account despite no active projects showing in Console. Already paid multiple times, keeps reappearing. No response from support for days. Billing ID: 01B3C0-1899D2-F0DA8D.

• 
  Triman Kumar Saha (@T2872727) reported 39 minutes ago

  @gcloudpartners @googlecloud Urgent!!! I need help my Google Account got disabled by automated AI false positive error... this account is so much important to me and there's no human support.... please help Reference case id- 9-6635000040823

• 
  Lokesh jha (@Lokesh1jha) reported 43 minutes ago

  @whyrohitwhy @googlecloud Even the gemini also did great work in deployment,I moved my FE from Vercel to Azure container App, Domain was on Cloudflare. It looked on all tabs and solved the issues. Later it got dizzy, may be free plan limits ,but it was really helpful. I needed that to be done overnight.

• 
  abzal gylymbai (@abzalgylymbai) reported 44 minutes ago

  @googlecloud Recurring unexplained charges (~$83, repeating) on my Google Cloud Billing account despite no active projects showing in Console. Already paid multiple times, keeps reappearing. No response from support for days. Billing ID: 01B3C0-1899D2-F0DA8D.

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

• 
  abzal gylymbai (@abzalgylymbai) reported 45 minutes ago

  @googlecloud @mirendil @nvidia Recurring unexplained charges (~$83, repeating) on my Google Cloud Billing account despite no active projects showing in Console. Already paid multiple times, keeps reappearing. No response from support for days. Billing ID: 01B3C0-1899D2-F0DA8D.

• 
  ofPowerofWant (@ofPowerofWant) reported 45 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

• 
  Garrett Smith (@gsmithw91) reported 46 minutes ago

  @googlecloud billing support case 70049182 I have reached out over 36 times over the past three months to get a refund for a error that Google claimed was their fault

• 
  Brad Bonin (@cisco_brad) reported 46 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.

• 
  Ffeennddeerr (@ffeennddeerr) reported 47 minutes ago

  Hi @googlecloud @GoogleDevs @Firebase ! My account disabled by mistake (false-positive bot detection) after travel. I'm trapped in a deadlock (SMS code doesn't send/'too many attempts'). Ticket ID: Case 10414028. Can someone please help escalate this? 4 months of work is stuck.

• 
  Jon Clark (@JonLClark) reported 50 minutes ago

  @VeryWellVersed @googlecloud WTF I thought losing my twitter handle to crypto spammers was upsetting 😱

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

• 
  Garrett Smith (@gsmithw91) reported 52 minutes ago

  @googlecloud @ThomasOrTK can someone help me get some accountability for a $3118.19 refund that I have been waiting 93 days for ?

• 
  CJ🇺🇸✝️✡️☪️ (@CJ46724511) reported 55 minutes ago

  @MLB @googlecloud 84mph lollipop down the center of the ****** pipe. Lol

• 
  atul joshi (@ajoshi31) reported 1 hour 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