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 |
|---|---|
| Jewar, UP | 1 |
| Montataire, Hauts-de-France | 1 |
| Greater Noida, UP | 1 |
| Ribeirão Preto, SP | 1 |
| Tijuana, BCN | 2 |
| Noida, UP | 1 |
| Capitán Sarmiento, BA | 1 |
| Sheridan Park, WA | 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:
-
MECH AI (@mech_app) reported@googlecloud URGENT ESCALATION: CRITICAL PRODUCTION OUTAGE – DAY 3 I am requesting an immediate status update and escalation of this ticket. We have been waiting 3 days for a resolution to a backend Google billing desync bug, and this is causing catastrophic damage to our business. To be absolutely clear, the API failure ("No available credits") is a verified bug on Google's end regarding our Tier 3 Post-Pay linkage. I have completely exhausted all possible client-side workarounds, including creating a brand new GCP project to force a fresh billing link. Nothing works. Business Impact Metrics: Downtime: 72+ hours of complete disruption to our core application feature (wiring diagrams). User Impact: Over 30,000 Daily Active Users (DAU) are currently affected and locked out of the service. Direct Revenue Loss: We have already processed over 20 canceled user subscriptions directly citing this disruption, and our support inbox is flooded with angry customers. Account Value & Next Steps: My companies have spent thousands of dollars annually on Google Cloud over the last two years, in addition to spending multiple thousands of dollars every single month on Google Ads. If this backend bug is not manually overridden or fixed today, I will be forced to immediately migrate our application to a different AI provider. Furthermore, due to the severe lack of operational reliability and support response, we will begin the process of pulling all of our business and infrastructure entirely out of the Google ecosystem. We cannot operate with a provider where a backend billing bug causes multi-day production outages. Please escalate this to an Engineering Lead or a Technical Account Manager immediately and provide a status update today.
-
Blend America 🇺🇲 (@blendamerica) reported@GoogleAIStudio Nothing, I am currently blocked from publishing my latest updates from AI Studio to Cloud Run due to a recurring deployment failure. Cloud Run support pointed to @GoogleAIStudio for support. @googlecloud
-
Jason Newton (@sleep_deprivado) reported@GoogleDeepMind @googlecloud hey @sundarpichai put together an application for android that uses ai - don't ask an llm or ping anybody who put it together. When you come back from that, fire the heads of product responsible for the mess and consolidate firebase, vertex ai, gemini api, google ai studio, bad
-
Say No To Trading (@SayNoToTrading) reported@ServiceNowNews @googlecloud Can they fix $NOW share price?
-
A Shah (@Arun1Shah) reportedHi @googlecloud @GoogleCloudTech , I have been waiting 18 days just to change the billing account on my Developer Program profile to access my Gen AI credits. Support keeps merging my tickets with zero resolution or ETA. Can someone please escalate Ticket #4857482?
-
Zero // (@__________kiwi) reported@Ravensong666 @googlecloud I’m also having this issue with Gemini and ChatGPT. Any alternative out there not doing this? I’m also use Claude
-
olifog (@fogelin) reported@andy_pavlo @googlecloud @CMUDB never felt more jealousy for an undergrad course
-
Chris (@everestchris6) reported@googlecloud a leaked api credential caused anomalous places api charges on my account, support is apparently processing the adjustment, but your billing system just auto-attempted 18× $180 charges in 5 mins, can someone get this resolved asap??
-
Machina Ratiocinatrix (@Machina_Ratio) reported@nlycskn @googlecloud Don't you even try to convince any sane professional that GCP is worth their effort of using (not to say paying for). It is an absolute pile of ****!
-
Krishnav Kanoi (@KanoiKrishnav) reported@vnsh02 @googlecloud It’s very bad I tried to use it , I have checked all available sites and APIs , nothing come remotely close to Google maps
-
Ryan Nixon (@rnixon92) reported@MyTechMusings @googlecloud Worth flagging though: inferring meaning from query logs assumes current usage = correct usage. That quietly bakes in tribal knowledge and historical bad joins. Powerful for discovery, but you end up with the 'common' answer, not necessarily the 'correct' one.
-
Slyy (@Slyy_007) reported@solana @googlecloud Damn this is huge ngl
-
Viktoria (@Viktoria5z) reported@GoogleCloud First-time Vertex AI user. Had €1,100 in free credits. Believed they covered my usage. Instead got charged €2,199. Immediately contacted support — agent said "it's being handled, no action needed." Woke up 6hrs later: €7,300+. I need urgent help
-
Leon (@OhHarshit) reportedHey @GoogleCloud, I’m a student and have an outstanding billing issue (~₹6k) from unintended VM instances due to a console issue. My billing account is now closed so I can’t access support. Could someone please help me get this reviewed? 🙏
-
Chen Avnery (@MindTheGapMTG) reported@googlecloud $750M to help people build agents. Almost none of it will fund the constraint and audit layers that stop those agents from going rogue at 3am. The bottleneck was never creation. It's governance after deployment.