Google Cloud Outage Map
The map below depicts the most recent cities worldwide where Google Cloud users have reported problems and outages. If you are having an issue with Google Cloud, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Google Cloud users affected:
Google Cloud Platform, offered by Google, is a suite of cloud computing services that runs on the same infrastructure that Google uses internally for its end-user products, such as Google Search and YouTube.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Guayaquil, Guayas | 1 |
| Mexico City, CDMX | 1 |
| Chhindwāra, MP | 1 |
| Los Angeles, CA | 1 |
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:
-
Shinka - AI (@ShinkaIoT) reported@DataChaz @googlecloud making agents guess workflows instead of giving them rails is why they flame out in ****, adk 2.0 locking down the backend is the fix we needed
-
身是业的根 (@muyang14756529) reportedUrgent! 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!thanks
-
teo (@teodorio) reportedHey @googlecloud BigQuery web UI is broken in production for every single user and you just bombed my planning presentation. Thanks!
-
Viraj Kokane (@virajkokane_) reported.@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?
-
ray (@raycruz_fk_maga) reported@googlecloud retarded posted ai wont do **** because ai cant fund the issue the outage is because poor funding
-
Alex Boudot (@the_alex_boudot) reported@NewsFromGoogle @googlecloud @Verizon Verizon users will meet Gemini as the outage that never happened.
-
NaoX | Post-Quantum Chain (@NaoXprotocol) reported@rjmuneeb101 @googlecloud Exactly. Migration is the trap door. Building it in from day one just sidesteps the whole problem.
-
Bernaridho Hutabarat (@bernaridho) reported@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?
-
Usman Bashir (@usman_basheers) reported@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?
-
Cryptic (@Cryptic_Web3) reported🚨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.
-
Prashanth Vaidya (@thecodemarathon) reported@GoogleCloud_IN @googlecloud Have DMed, please include the reason why a verification failed rather than asking the customer to redo the verification blindly again and again!
-
abzal gylymbai (@abzalgylymbai) reported@googlecloud @wiz_io 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?
-
身是业的根 (@muyang14756529) reported@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
-
Viraj Kokane (@virajkokane_) reported@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?
-
Antonio Gomes (@onchainantonio) reported@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.