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 |
|---|---|
| Noida, UP | 3 |
| Little Rock, AR | 1 |
| Jewar, UP | 1 |
| Montataire, Hauts-de-France | 1 |
| Greater Noida, UP | 1 |
| Ribeirão Preto, SP | 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:
-
Aging Shadow (@AgingShadow) reported@MLBStats @googlecloud For bleep sake it was against the worst team in MLB. A team that leads all of baseball in striking out! Geezus!
-
Slyy (@Slyy_007) reported@solana @googlecloud Damn this is huge ngl
-
Yanick Nde (@ndeyanick) reported@googlecloud Cloudbuild is broken again remote: Invalid username or token. Password authentication is not supported for *** operations.
-
ashen (@ashen_one) reported@SolanaFndn @googlecloud hell yea wtf
-
Riccardo Dana | @SWOP (@riccardo_dana) reportedSWOP is back online. On a side note, we have decided to migrate our servers from AWS to @googlecloud this is not the first time AWS has had issues and as a start up we cant afford to have downtime. Thank you to our swopers for your patience.
-
teqqed (@teqqed) reportedwhy are configured spend limits not respected @googlecloud? instead of stopping the service when limits are reached you just keep going and move the bill to the next month? gtfoh
-
Kundan (@Kundan1243752) reported@googlecloud I desperately need an escalation for Case #70946233. I am a student who accidentally left an empty Cloud SQL instance running. Support kindly waived 50% but sent the rest to collections. I have never held a job and have zero income. I physically cannot pay this.
-
kingson (@kingsonGEGE) reported@nvidia @googlecloud This is the interesting privacy shift: private AI stops being only “whose model is best” and becomes a verifiable supply-chain problem. Compute, attestation, logs, data boundaries, and public ledgers are the product now. The lock icon finally has infrastructure behind it.
-
aira (@airasentia) reported@rseroter @googlecloud agent revisions are where the chat demo grows up. traffic splitting sounds boring until one bad prompt revision starts touching real tools.
-
Maarten de Lange (@RCM_Doherty) reported@JustJake Jake, don’t worry too much. It was annoying, but you provide great service and results. Thats not wiped out due to a few hours of disruption. Having said that, it’s just crazy how little @googlecloud cares about its customers, you could consider leaving them on the long run.
-
Anu. Father to Giga Chad (@JamesMc72191769) reported@birdeye_data @googlecloud @ProductHunt Ok be honest. How many reading this has ANY IDEA WTF IT MEANS?
-
Aditya Jethani (@okaditya84) reported@googlecloud I have sent a DM for regarding the issue. Hoping for a resolution.
-
Ferbin (@Ferbin08) reported@rseroter @googlecloud when you run trading bots under burst load, this is real. you're stuck choosing between idle capacity or slow starts. but standby buffers cost something too - what's the overhead when you scale across regions?
-
teqqed (@teqqed) reported@googlecloud i did but apprently have to wait for support to respond. regardless of the outcome, we should switch to @Mapbox it seems
-
Shayan Mashatian (@shayanrm) reported@_oliveiradanilo @googlecloud At minimum, they must make spikes in cost or usage notifications a default. Until they don’t do that, there is a huge risk in using Google Cloud for anything, even a simple database set up on Firebase. Specifically with so many vibe-coders and AI assistants everyone is using. AI coders have a tendency to suppress errors, and create fallbacks. They can easily create a circuit, go unseen for days and account owners end up with $$$$$$$ bills.