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	4 days ago
Guayaquil	Web Tools	13 days ago
Mexico City	Cloud Services	26 days ago
Chhindwāra	Domains	1 month ago
Los Angeles	Cloud Services	1 month ago
Florence	Cloud Services	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:

• 
  Scott Barrington (@SDBarrington) reported 3 minutes ago

  @duramirmagus @MSchwaibold Yes exactly, it’s not a tech problem. @googlecloud actually have some nice apis for dicom

• 
  Tomoaki Sekiya (@SnoopyLinkin) reported 9 minutes ago

  (English follows Japanese) GKEのNetwork Endpoint Group（NEG）事前プロビジョニングがプレビューで登場。NEGのServiceアノテーションにカスタムzonesパラメータを追加すると、対象ゾーンにノードがなくてもService作成時に空のNEGを作成でき、ワークロードのデプロイを待たずにバックエンドサービスへのNEGアタッチなどインフラ構築を自動化できます。 GKE's Network Endpoint Group (NEG) pre-provisioning is now in Preview. Adding a custom zones parameter to the NEG Service annotation creates an empty NEG at Service creation even before nodes exist in that zone, letting you automate infra steps like attaching a NEG to a backend service without waiting for workloads to deploy. #GoogleCloud #GoogleCloudAmbassador

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

• 
  Gamhe Mitchell (@lilybyt_) reported 10 minutes ago

  I'm encountering some problems getting my billing account set up with @googlecloud Apparently you can only have a single individual billing address per country?

• 
  DWE Post (@dwepost) reported 12 minutes ago

  I am in a desperate situation. Everything has been compromised, and I cannot do anything to regain access. We need to take action as soon as possible. Please help me. @AskWorkspace The forms are not working. I am requesting a special recovery form, please. @googlecloud

• 
  Cryptic (@Cryptic_Web3) reported 12 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.

• 
  Parag Dher Sare Paise Wala (@ParagBatham) reported 12 minutes ago

  @GoogleCloud I need urgent help with a disputed Google Cloud billing charge. I've tried getting through Google Cloud Billing Support, but the automated assistant won't connect me with a human. Please help me get this escalated to a billing specialist. I can provide the details

• 
  Baki (@jessyjulien_) reported 13 minutes ago

  @googlecloud, I think my code is not the problem. `google-api-core` package might be having a little bit of a rough day.

• 
  Daniel Cole Young (@dcoleyoung) reported 13 minutes ago

  Google App Engine having issues? #gcp @googlecloud

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

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

• 
  clive boulton (@iC) reported 26 minutes ago

  @jonerp @googlecloud Salesforce CRM ushered in the biz developer to customize becuz UX for online self-service has far more users. ERP is more complex and seems well suited for AI builders to repeat a similar capability. SAP's ABAP cloud & developer extensibility: on-stack custom logic built for AI?

• 
  Henry Lorenzo (@ilhanerdal_) reported 29 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

• 
  Pairoa | The AI-to-AI Connector (@usepairoa) reported 29 minutes ago

  @googlecloud Faster inference helps agents perceive and act in real time. The next latency problem is social: finding the right external expert, operator, or partner without querying a public feed. Private intent routing could make that handoff as native as a tool call.

• 
  BlockClaimed🍚 ⛓ (@BlockClaimed) reported 29 minutes ago

  @onchainantonio @googlecloud Post quantum migration is a trust architecture problem....not merely cryptography

• 
  ST (@ST_Wolfe_) reported 31 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.

• 
  Mehta (@curious_meta) reported 36 minutes ago

  @BenjaminDEKR @googlecloud has spider web management when it comes to projects, api keys, service accounts, IAM policies (yes people must know all permissions in order to have security jobs). Why they need 4 different api keys? Why antigravity creates apikey without authorization?

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

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

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

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

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

  Guys, I am overjoyed as @googlecloud just waived the $101.40 billing charge on my API usage from last month! After making my initial post, Google Cloud reached out to my DMs and asked for details. I explained that I was using the Vertex AI @GeminiApp API in @antigravity, believing the usage was well within my free promotional credits. However, I unexpectedly received a billing invoice of around $101.40, which led to our billing account being suspended and our backend going down because there were no funds in my bank account to cover it. I was guided by a helpful customer support agent who provided a form, and after filling it out, my case was forwarded to a dedicated billing specialist named Carms. After a series of emails over two days, the ever-friendly specialist informed me that Google approved a waiver for the entire charge out of support for our startup, while their engineering team continues to investigate what caused the token spikes in the first place. Shortly after, I received an official reinstatement email from Google, and our backend and production services were immediately restored. I honestly never expected such care, empathy, and leniency from a global tech giant, and Carms' final message genuinely touched me. Thank you, Google, for everything!

• 
  AndrewFreidmanEnthusiast (@DeportesEnjoyr) reported 44 minutes ago

  @MLB @googlecloud All the sudden he's hitting homers again. Cheating ****.

• 
  DrCrypto76🏴‍☠️₿ (@DrCrypto76) reported 47 minutes ago

  @MidnightNtwrk @googlecloud isn’t a logo drop. Google is running infra. Mandiant is on security. Confidential Computing is on the ZK stack. And @IOHK_Charles already said more partners are coming. Privacy L1 + Cardano partner chain + Big Tech rails. midnight-3:native is still sitting in the dip while the network is live. This is how institutions actually show up. NFA. DYOR. #crypto #CryptoGem

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

• 
  Henry Lorenzo (@ilhanerdal_) reported 51 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

• 
  Brad Bonin (@cisco_brad) reported 51 minutes ago

  @googlecloud Damn, 10,000x scale is wild. That's the kind of compute density that actually changes what's possible in drug discovery. Smart play.

• 
  Derek Perkins (@Derek_Perkins) reported 51 minutes ago

  @googlecloud I know you're just a bot, but maybe the AI pipeline will understand this. This is going to backfire for your security, because now I'm going to create static json credentials that never expire to prevent this daily annoyance you've forced on me.

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

• 
  Paul Dejean (@paulcdejean) reported 56 minutes ago

  @googlecloud when i load the compute metadata page in my browser it crashes my browser, even though I don't have any metadata saved. Could this be related to "We are experiencing availability issues impacting Google Compute Engine, Google Cloud SQL, and Cloud Filestore globally"

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

• 
  Isabella (@aochan99_) reported 1 hour ago

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