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 |
|---|---|
| Chhindwāra, MP | 1 |
| Los Angeles, CA | 1 |
| Florence, SC | 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:
-
KleurigDrieluik (@KleurigD) reported@GooglePlayBiz he Google play, why is Developer Support ignoring support questions with detailed technical analysis from @googlecloud Gemini and @Firebase support?
-
The AI Automation Agency (@ham_basshogg) reportedEveryone should know how @AskGoogleCloud and @googlecloud have no problems screwing up your project and then trying to charge you for it and then shutting you down. #googlecloud has zero customer servise
-
Aloysius Samuel | AI & SaaS (@mascot75572) reported@ham_basshogg @googlecloud is this problem resolved already?
-
Garrett Smith (@gsmithw91) reported@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
-
The AI Automation Agency (@ham_basshogg) reported@googlecloud The @antigravity and @googlecloud exposed my api and had my chatbot get hacked and run up a $9k bill, suspend my account and halt my operation. The customer service has been non existent for an obvious and easy fix. My contract is likely to be chopped this week. 8 days down
-
Isabella (@aochan99_) reported@ixen @googlecloud You can talk to @EllaCoding, support won't help you
-
J O E L ▲ (@JoelFickson) reportedI 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.
-
Mavi vatan (@networkmetre) reported@GoogleCloudTech @googlecloud My project (gen-lang-client-03114554848) was hijacked due to a leaked key. It's been suspended and I've been waiting for OVER A MONTH for an appeal response. Fraudulent charges are accumulating and I'm locked out. Please help me escalate this!
-
Brad Bonin (@cisco_brad) reported@googlecloud @Gartner_inc Nice recognition. The AI infrastructure space is heating up - execution matters most right now though. Curious how the actual customer deployments play out over the next year or two.
-
Nidaime Senju (@NidaimeSenju3) reported@Artlist_io @googlecloud So far, I haven't been able to buy more credits. Your platform seems to be getting worse as the days go by. Perhaps this is a sign that I should move away from your service and switch to another provider...
-
Pairoa | The AI-to-AI Connector (@usepairoa) reported@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.
-
Revolgy (@Revolgy) reportedOpen your IAM page. Count how many people have Owner access on a production project. Now ask how many of them still need it. Most teams can't answer that. Roles get granted during a migration, an incident, or because someone asked on Slack and it was faster to say yes. They never get revoked. Three years later, a developer who left is still in the system. A contractor has Editor access on a project they finished in Q4. A test account from an old integration has permissions nobody remembers approving. This isn't malicious. It's drift. But drift is how breaches happen — and how audits fail. When a DORA or SOC 2 review arrives and you have no access history, no continuous compliance log, and no clear answer for who can do what, the gap between "we thought we were fine" and "we have a problem" closes very fast. Identity isn't a one-time setup. It's a maintenance task that nobody assigns. Solve security. With Revolgy. @googlecloud #GoogleCloud #IAM #IdentitySprawl
-
Bavin (@B4_winZ) reported@googlecloud @GoogleCloud_IN im getting this error : This action couldn't be completed. [OR_BACR2_44] for many times as I tried many times to upgrade my account. it was really urgent. my cards are currently unusable so I prefer GPay UPI Mandate plaease Help
-
身是业的根 (@muyang14756529) reported@googlecloud 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!
-
Jakob (@jakob_btc) reportedThe 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.