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 (67%)
• Domains (17%)
• Web Tools (17%)

Live Outage Map

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

City	Problem Type	Report Time
Catania	Cloud Services	11 hours ago
Guayaquil	Web Tools	9 days ago
Mexico City	Cloud Services	22 days ago
Chhindwāra	Domains	29 days ago
Los Angeles	Cloud Services	30 days ago
Florence	Cloud Services	2 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:

• 
  J O E L ▲ (@JoelFickson) reported 1 minute 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.

• 
  Decisively Digital (@DcyDigital) reported 2 minutes ago

  @effiekav @googlecloud The moat is permissions, provenance and escalation paths, not model IQ. Most enterprises will find the bottleneck was never AI, it was that nobody could say who may do what.

• 
  Conrad Lotz (@conradlotz) reported 5 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?

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

• 
  Triman Kumar Saha (@T2872727) reported 5 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

• 
  Triman Kumar Saha (@T2872727) reported 7 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

• 
  Aka4real (@Aka_olisa_) reported 8 minutes ago

  @googlecloud Why this matters for Google: Developers and early-stage startups are being forced to migrate to competitors (like AWS, which has introduced local NGN billing support) simply because we cannot physically pay Google.

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

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

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

  @sundarpichai @GoogleWorkspace 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

• 
  zbt3sup (@zbt3sup1) reported 20 minutes ago

  @intel @googlecloud Bad choice for your engineers

• 
  Garrett Smith (@gsmithw91) reported 28 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.

• 
  Mankaran (@MankaranSInghK2) reported 31 minutes ago

  @Google @GoogleCloud @sundarpichai I feel ROBBED. I paid for Google Cloud to learn and build, but I’ve been locked out of my Google account for days. My restoration was approved, yet verification still fails. Cloud Support closed my case and sent me in circles.

• 
  Henry Lorenzo (@ilhanerdal_) reported 31 minutes ago

  $GOOGL ’s Q2 results produced the most profitable quarter in Alphabet’s history: $112.1B in net income—the company’s first quarter above $100B. But that headline needs context. Most of it came from unrealized gains in Alphabet’s equity portfolio, likely driven largely by its stakes in $SPCX and Anthropic. At the same time, $44.9B in CapEx pushed quarterly free cash flow to negative $5.9B. That is what the market focused on. The number I keep coming back to is Google Cloud’s $514B backlog—nearly 5x what it was a year ago. Demand is not the problem. Capacity is. Google still does not have enough compute and data-center capacity to serve that demand, so I believe management is right to keep investing aggressively. The buildout is pressuring free cash flow today. But if it unlocks even a meaningful portion of that backlog, investors may eventually view this spending very differently. The real question is not whether demand exists. It is how quickly $GOOGL can build enough capacity to capture it. #GOOGL #GoogleCloud #AI

• 
  Viraj Kokane (@virajkokane_) reported 33 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?

• 
  Gleb Otochkin (@sky_vst) reported 33 minutes ago

  @MShteyn5470 @rseroter @googlecloud Out of curiosity - how would you warm up a public global service endpoint? It serves thousands requests per second all the time and you never really know what backend serves your particular request.

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

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

• 
  Kat MacSpyro (@KatSpyroMacD) reported 37 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.

• 
  Zodiac (@Zoddiacc) reported 38 minutes ago

  My app's Google Cloud project got suspended today. Reason: "abusive activity consistent with hijacking." Turns out an API key shipped in the app binary got scraped and someone used it to spin up resources on my project. Already deleted the key, filed an appeal, ticket's just sitting there. App's fully down for users in the meantime. @googlecloud any way to speed this up?

• 
  Ricard Gardella (@RicardGardella) reported 41 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? 👇

• 
  Abdullahi Adam Usman (@Abdalla_Nangere) reported 44 minutes ago

  Starting up a business is not easy. You will be building, trying to keep things running, and then @googlecloud will suddenly slam you with a $101 invoice for API usage. Now, where do you even begin to service that? This is something I have not even finished building, let alone started making profits from. May Allah see us through. It is really not easy. Ya Allah.

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

  Another day, another need to 'unsubscribe' from @googlecloud marketing emails. This is why I've fully removed myself from all things @Google - they treat everyone with complete contempt, refuse to honor preferences, and are happy to **** you as a customer at every opportunity.

• 
  ST (@ST_Wolfe_) reported 45 minutes ago

  1. The Engine is Built and Dyno-TestedThe actual software engine (the /verify flow on @googlecloud using cryptographic keys and @solana scoring) is fully built, bolted down, and running reliably. It works.

• 
  GovTechNow (@govtechnow) reported 46 minutes ago

  @googlecloud The problem is, the potential rug pull when venture funding dries up and the real cost gets passed on, eventually to the public.

• 
  Shailendra Varma (@_shailendra_var) reported 48 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. 🙏

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

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

  @googlecloud @shaunwhite Urgent! My business is down because @GoogleCloud suspended project lateral-journey-450812-g7. Live tokens expire in hours, causing permanent data loss. Support escalated but compliance is silent. Need human help for Ticket 2XWJSBKNPMM7QOD3U5KVHZU5WI!

• 
  abzal gylymbai (@abzalgylymbai) reported 53 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. Can someone please DM me / escalate this?

• 
  Mathieu Kessler (@mayeu20) reported 53 minutes ago

  @googlecloud Embedding agents directly into network products is a strong integration.

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