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 (43%)
• Domains (29%)
• Web Tools (14%)
• Hosting (14%)

Live Outage Map

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

City	Problem Type	Report Time
Guayaquil	Web Tools	17 hours ago
Mexico City	Cloud Services	14 days ago
Chhindwāra	Domains	21 days ago
Los Angeles	Cloud Services	21 days ago
Florence	Cloud Services	2 months ago
Noida	Hosting	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:

• 
  abzal gylymbai (@abzalgylymbai) reported 5 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.

• 
  KleurigDrieluik (@KleurigD) reported 5 minutes ago

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

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

• 
  Adel Bucetta (@adelbucetta) reported 15 minutes ago

  @googlecloud nokia's move isn't just about automating their network, it's about creating a whole new layer of abstraction for telecom infrastructure. now imagine if this tech trickled down to edge cases like rural networks or even smart cities

• 
  Rooke Poole (@rookepoole) reported 18 minutes ago

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

• 
  Revolgy (@Revolgy) reported 23 minutes ago

  Nothing changed. That's the problem. An idle environment nobody noticed running for six months. A staging server promoted to **** and forgotten. A license for a person who left the company in February. A BigQuery job running every hour. Nobody knows why. Finance asks why costs went up. Engineering says nothing changed. Both are right. The bill isn't lying. You just can't see what's inside it. Cutting the number is the easy part once you know what you're actually running. Most teams don't know. They find out when the invoice arrives and work backwards from there. We build visibility first. Cost follows. Solve cost. With Revolgy. @googlecloud #GoogleCloud #Revolgy #ManagedServices

• 
  200divesL8r (@200divesL8r) reported 24 minutes ago

  @googlecloud Yeah, your product sucks bro!

• 
  Adel Bucetta (@adelbucetta) reported 26 minutes ago

  @googlecloud the honest answer is that many companies think they can just bolt ai on top of their existing data mess, but it's not that simple. you need a robust data strategy from day one to support autonomous agents.

• 
  Brad Bonin (@cisco_brad) reported 27 minutes ago

  @googlecloud Code review becoming the actual bottleneck is wild. Guess we're trading one problem for another, but at least the hard part (ideation) moves faster. Need smarter filtering before human eyes touch it.

• 
  Siddharth Jaiswal (@sdrth) reported 30 minutes ago

  @Analyticsindiam @googlecloud Your lovable built website is leaking user data. Sent you a DM and Email on 11th. Please fix.

• 
  Scooperleash_usa llc (@scooperleash) reported 31 minutes ago

  when cloud network is controlling what your company get at what time, that autonomy is cruel especially when it becomes like the company data that is stored in @googlecloud belongs to the cloud instead of the platform that uses the cloud

• 
  Shailendra Varma (@_shailendra_var) reported 32 minutes ago

  🚨 URGENT REQUEST — Please Expedite My Project Reinstatement My Google Cloud project supporting Tailor Book has been suspended, and the entire app backend is currently down. Because of this, thousands of tailor businesses using the app are unable to manage their shops and daily work. My case has already been escalated to the internal team for project reinstatement, but the process is taking time while our users are completely dependent on the service. 🎫 Case ID: WRUOFYRHZ3ARFV4H6U2YBMRYEA @GoogleCloud @Firebase Please review my case and expedite the reinstatement process. This is a live production application, and every additional day of downtime is directly affecting real businesses. I understand that security reviews take time, but I urgently request your help in restoring the project as soon as possible. 🙏

• 
  Leomar Osorio (@osorioleomar) reported 33 minutes ago

  Hi @askgcp @googlecloud, our CPTO has paused our company's GCP migration after a known Firebase API vulnerability led to 19k SEK in unauthorized Gemini charges. We provided proof of external abuse but haven't heard back in over a week. Need immediate help with Case #72859549

• 
  Bally_AgenticAI (@bally_kehal) reported 34 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

• 
  Rishi (@RishiC19) reported 36 minutes ago

  Is there any @googlecloud support available for an account/project regarding startup credits?

• 
  Scooter 5150 (@5150Scooter) reported 36 minutes ago

  @googlecloud Anyone else concerned about the "employees" signing a letter to urge US to slow development of AI? Sounds like it would give China advantage with AI.

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

• 
  Pol (@pol_refwgtrtgr) reported 39 minutes ago

  @sammathews @Bl0soom @googlecloud You waste money on that **** and then you need 750 months to pay for a player. Cringe asf

• 
  J O E L ▲ (@JoelFickson) reported 40 minutes ago

  I need to share my horrible experience with @googlecloud and their lack of support in resolving an issue that's been sitting since April. And how someone from support decided to close the case without resolving it.

• 
  CEOInterviews.AI (@CEOinterview) reported 42 minutes ago

  The market spent this month betting AI capex will never earn its return. Alphabet's Wednesday earnings are the first hard rebuttal. Google Cloud operating income hit 8.8 billion dollars, triple the 2.8 billion of a year earlier, on 82 percent revenue growth. Back in April, Google Cloud CEO Thomas Kurian told Matthew Berman why he was not worried: in a capacity constrained market, owning your own chip keeps your unit economics attractive while everyone else pays up. Google is now selling that chip to Anthropic, OpenAI and Meta. Source: $GOOG @googlecloud, Matthew Berman @MatthewBerman

• 
  Garrett Smith (@gsmithw91) reported 42 minutes ago

  @Google Is there anyone that can help with a cloud billing support case I have been waiting 93 days to resolve. I have been expecting a refund of $3118.19 @googlecloud billing support has not been accountable or helpful one bit

• 
  Evan Kirstel #B2B #TechFluencer (@EvanKirstel) reported 44 minutes ago

  @googlecloud Reading hundreds of open ended comments is the job everyone fakes. The risk is it smooths out the one angry comment that was the actual signal. Useful when it shows you outliers, not averages. Want to come on my podcast and talk about it?

• 
  Ricard Gardella (@RicardGardella) reported 46 minutes ago

  Fixed a sneaky Terraform @HashiCorp @googlecloud bug in Magic Modules: @GoogleCloudTech Problem: Setting enable_proxy_protocol = false after it was true didn't send the update to the GCP API properly. What was wrong? 👇

• 
  EDJ (@edj_FL) reported 46 minutes ago

  @MLB @googlecloud @CleGuardians Too bad the Guardians offense is absolutely atrocious

• 
  busch propaganda spreader 🇺🇸 (25-12) (@Nazar4Bedard) reported 46 minutes ago

  @StudiosLA90210 @MLBNetwork @googlecloud Your fanbase sucks and he was right cry about it

• 
  Garrett Smith (@gsmithw91) reported 47 minutes ago

  @googlecloud I have been having a billing issue for 90 days now in which i was charge $3000 improperly. You guys have admitted it but I still haven't received my refund and have had a hard time getting any follow up at all regarding the case. CASE 70049182

• 
  Bernaridho Hutabarat (@bernaridho) reported 47 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?

• 
  Cryptic (@Cryptic_Web3) reported 52 minutes ago

  🚨NEW: @selfxyz and @usat, with support from @googlecloud, have launched a stablecoin distribution program on Celo that verifies each recipient is a real, unique person before sending tokens. Users can verify their identity with a passport through Self’s privacy-preserving, zero-knowledge system, allowing the faucet to distribute the dollar-backed USA stablecoin without storing or publicly exposing users’ personal information.

• 
  Zachary Rand (@therealZOAT) reported 53 minutes ago

  @testingcatalog My company's Gemini Enterprise UI never looks like what you or @googlecloud post.

• 
  Viraj Kokane (@virajkokane_) reported 58 minutes ago

  .@GoogleCloud @GoogleStartups @ragingdas We've been blocked for over 2 weeks trying to get a GPU quota approved for our production workloads. Every manual quota request is auto-rejected within seconds, with no explanation. Our assigned account manager has been unavailable for over a week, with no replacement. We've spoken to 3 different sales contacts, shared all requested details multiple times, and followed up repeatedly. Yet no meaningful update. Our platform has paying customers, and our render pipeline is effectively down because we can't provision the GPUs we need. We're not asking for special treatment - just a human review, transparency, and a point of contact who can help resolve this. We joined the Google for Startups program to build, not to spend weeks chasing responses. Can someone from the Google Cloud team please look into this?