1. Home
  2. Services
  3. Google Cloud
Google Cloud cloud.google.com

Is Google Cloud down right now? Live status and outage tracker

No, Google Cloud is up.

No outage detected, and no user reports in the last hour.

Live Last spike Data refreshes every 5 minutes
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

29 reports in total, counted in 15-minute windows

No problem reports came in for Google Cloud in the last hour, against about 4 at this time on a usual day. Over the last 24 hours there were 29 reports. Worldwide, most recent reports were about virtual machines (40%) and DNS (20%). The last spike in reports was 77 h ago and lasted 17 min. These are user reports from the US, where most people report Google Cloud problems.

Around the world right now: normal in 71 other countries. Most reports in the last hour: Brazil 2 · the UK 2 · India 1. By country

In the past 24 hours, 29 user reports came in for Google Cloud. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day. The busiest 15-minute window had 4 reports, about 23 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Reports, last hour
0
Quiet
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
4
4 reports, 23 h ago
Last 24 hours

Google Cloud outages and problems

In the past 24 hours, 29 user reports came in for Google Cloud. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 4 reports, about 23 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Google Cloud stayed at their usual level the whole time.
This month

Google Cloud in October 2026

Problem reports in October (since 7 October)
278

Monthly report for October 2026

What went wrong

What people said was wrong in recent problem reports for Google Cloud worldwide.

  1. Virtual Machines40%
  2. DNS20%
  3. API20%
  4. Databases20%

Share of 5 recent reports that said what was wrong, from every country listed below.

World map

Google Cloud reports around the world

In the last 24 hours, 156 problem reports about Google Cloud came in from 27 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
Brazil Normal 250
The UK Normal 25
India Normal 17
Germany Normal 11
The US numbers above Normal 047
France Normal 06
Argentina Normal 04
Thailand Normal 04
Canada Normal 03
Belgium Normal 03
Japan Normal 03
Greece Normal 03

Each country's status compares its reports with the usual level there. 60 more countries had 20 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Google Cloud problem spikes, last 30 days

Since 7 October, Google Cloud had 1 outage spike and 1 period of elevated reports. The longest lasted 17 min, on 28 October.

  • Fri 2 Oct: no data
  • Sat 3 Oct: no data
  • Sun 4 Oct: no data
  • Mon 5 Oct: no data
  • Tue 6 Oct: no data
  • Wed 7 Oct: 1 report
  • Thu 8 Oct: 1 report
  • Fri 9 Oct: 0 reports
  • Sat 10 Oct: 0 reports
  • Sun 11 Oct: 1 report
  • Mon 12 Oct: 0 reports
  • Tue 13 Oct: 0 reports
  • Wed 14 Oct: 4 reports
  • Thu 15 Oct: 3 reports
  • Fri 16 Oct: 0 reports
  • Sat 17 Oct: 0 reports
  • Sun 18 Oct: 0 reports
  • Mon 19 Oct: 2 reports
  • Tue 20 Oct: 134 reports (outage spike that day)
  • Wed 21 Oct: no data
  • Thu 22 Oct: 0 reports
  • Fri 23 Oct: 5 reports
  • Sat 24 Oct: 1 report
  • Sun 25 Oct: 0 reports
  • Mon 26 Oct: 0 reports
  • Tue 27 Oct: 1 report
  • Wed 28 Oct: 18 reports (elevated reports that day)
  • Thu 29 Oct: 39 reports
  • Fri 30 Oct: 54 reports
  • Sat 31 Oct: 14 reports
  • Elevated reports
    Wed 28 Oct, 15:41–15:58
    Lasted 17 min
    11peak reports
  • Outage
    Tue 20 Oct, 13:29–13:44
    Lasted 15 min
    12peak reports

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • Brazil127
  • The US120
  • France23
  • Mexico21
  • The UK20
  • Canada15
  • India15
  • Japan13

Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 7 October 2026. Monthly reports for all services

Troubleshooting

How to fix Google Cloud not working

Google Cloud is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach cloud.google.com over your own connection, right now. Nothing is sent to us or stored.

  1. Check Cloud Console status indicators

    Open the official status page first. Filter by Compute Engine or Cloud Storage because Console often loads while one API fails, so you can tell a broad outage from a project fault.

  2. Re-authenticate gcloud and browser session

    You lost your token. Run gcloud auth login in your terminal, then open Console again and pick the right account when you see an access denied or quota project prompt.

  3. Review billing, quotas and IAM permissions

    If BigQuery jobs stall or Functions reject your deploys, open Cloud Console and check Billing for your account state plus IAM and Admin > Quotas for API limits. Ask your admin for access.

  4. Switch region and inspect Cloud Logging errors

    Move regions to isolate the fault. Redeploy your workload in europe-west1 or us-central1, then open Logging > Logs Explorer in Cloud Console so you can copy the failure text for support.

While Google Cloud is down: what to use instead

  • gcloud CLI on your own machine When the Cloud Console hangs on a spinner or loads a blank dashboard, the command line tool on your laptop can often still reach the APIs, so you can list instances, restart a VM or read logs from your terminal.
  • A different region If the incident is limited to one region, move traffic to a zone elsewhere that you have already set up.
  • Google Cloud mobile app The Android and iOS app shows incidents and lets you stop or start Compute Engine instances, which helps when the browser console refuses to load.
  • AWS or Microsoft Azure This only works if you already keep a standby copy of your stack on that provider.
Your device

Fix Google Cloud on Windows, Mac, Android and iPhone

Google Cloud on Windows

Fix
Clear your web browser's cache and cookies, or update the Google Cloud CLI if you are experiencing command-line connection issues. Ensure your Windows Firewall or antivirus is not blocking Google Cloud's network traffic.
Check
Check the official Google Cloud Service Health Dashboard in your web browser to see if there is an active outage. You can also run network diagnostics to verify if your connection to Google Cloud's API endpoints is blocked.
Command Prompt
ping cloud.google.comTest whether Google Cloud's servers reply
nslookup cloud.google.comCheck that Google Cloud's DNS resolves
tracert cloud.google.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Google Cloud on Mac

Fix
Update your Google Cloud CLI installation and clear your browser's site data to resolve loading issues. Verify that your macOS firewall or local proxy settings are not interfering with Google Cloud services.
Check
Monitor the Google Cloud Service Health Dashboard using Safari or Chrome to check for ongoing service disruptions. You can also use network utility tools to test connectivity to Google Cloud API endpoints.
Terminal
ping -c 4 cloud.google.comTest whether Google Cloud's servers reply
nslookup cloud.google.comCheck that Google Cloud's DNS resolves
traceroute cloud.google.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Google Cloud on Android

Fix
Force stop the Google Cloud Console app, clear its cache and data in your device settings, and ensure the app is updated to the latest version. If the issue persists, switch from mobile data to a stable Wi-Fi network.
Check
Open the Google Cloud Console app to see if it displays connection errors or fails to load your project resources. You can also check the Google Play Store for recent app updates or user reports.

Google Cloud on iPhone and iPad

Fix
Restart the Google Cloud Console app and check the App Store to ensure you are running the latest version. If connectivity fails, toggle Airplane Mode or reconnect to a different Wi-Fi network.
Check
Launch the Google Cloud Console app on your iPhone or iPad to see if it fails to load your projects or shows connectivity alerts. You can also check the mobile web version of the Google Cloud status page.
Same time

Problems at the same time as Google Cloud

Since 7 October, all 2 of Google Cloud's spikes in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report Google Cloud problems

The busiest hour for reports about Google Cloud is 15:00 to 16:00 Central European time, and the busiest day is Tuesday.

By hour of the day

  • 00:00 to 01:00: 0.13 reports on an average day
  • 01:00 to 02:00: 0.25 reports on an average day
  • 02:00 to 03:00: 0.16 reports on an average day
  • 03:00 to 04:00: 0.21 reports on an average day
  • 04:00 to 05:00: 0.13 reports on an average day
  • 05:00 to 06:00: 0.08 reports on an average day
  • 06:00 to 07:00: 0.13 reports on an average day
  • 07:00 to 08:00: 0.13 reports on an average day
  • 08:00 to 09:00: 0.23 reports on an average day
  • 09:00 to 10:00: 0.14 reports on an average day
  • 10:00 to 11:00: 0.16 reports on an average day
  • 11:00 to 12:00: 0.45 reports on an average day
  • 12:00 to 13:00: 0.8 reports on an average day
  • 13:00 to 14:00: 0.92 reports on an average day
  • 14:00 to 15:00: 0.84 reports on an average day
  • 15:00 to 16:00: 1.3 reports on an average day
  • 16:00 to 17:00: 0.95 reports on an average day
  • 17:00 to 18:00: 0.71 reports on an average day
  • 18:00 to 19:00: 0.33 reports on an average day
  • 19:00 to 20:00: 0.61 reports on an average day
  • 20:00 to 21:00: 0.68 reports on an average day
  • 21:00 to 22:00: 0.72 reports on an average day
  • 22:00 to 23:00: 0.59 reports on an average day
  • 23:00 to 00:00: 0.26 reports on an average day

By day of the week

  • Monday: 0.59 reports on an average Monday
  • Tuesday: 31 reports on an average Tuesday
  • Wednesday: 7.7 reports on an average Wednesday
  • Thursday: 14 reports on an average Thursday
  • Friday: 15 reports on an average Friday
  • Saturday: 3.9 reports on an average Saturday
  • Sunday: 0.32 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when Google Cloud goes down

Google Cloud is a suite of cloud services. Companies and developers rely on it for hosting, data storage, analytics, and internal tools; an outage interrupts deploying apps, accessing virtual machines, reading logs, or managing databases, and this page shows whether user problem reports for it are above their usual level in 15-minute windows over the last 24 hours.

During an outage you may see the console fail to load, API calls return errors, Compute Engine instances stop responding, and Cloud Storage uploads or downloads stall. Some problems hit one region or one service first. Console and API issues surface before background jobs, because those interfaces handle sign-in, configuration, reads, and writes; a global dashboard can look calm while your project is broken.

Servers and network

Google Cloud IP address, servers and network

Checking cloud.google.com from our server…

Questions

Google Cloud FAQ

Is Google Cloud down right now?

The status at the top of this page shows whether user problem reports for the service are above their usual level, counted in 15-minute windows over the last 24 hours. If that number is climbing, plenty of people are hitting the same wall. Check the official status page for confirmation from Google. To work out whether the trouble is only on your side, load another site in the same browser, try the service from a second network such as a phone hotspot, and watch whether the failure follows you or stays put.

The Cloud Console won't load for me but gcloud commands still work. What does that mean?

Often the console is the only piece that is broken, since it is a web app talking to the same APIs your terminal reaches. If gcloud returns data while the browser spins, your credentials and project are probably fine. Clear the cache, sign out and back in, then try an incognito window; a stale session or a browser extension causes this more often than an outage does.

My Compute Engine VM is stuck on starting and I keep getting a quota error. Is that an outage?

A quota message means your project has hit a limit on CPUs or IP addresses in that region, and the instance will keep failing until you free resources or ask for more. It is a per-project ceiling, so everyone else on the service carries on as normal. The status page will not move for you on this one. Check the quotas page in the console and try a different zone.

Why do I get a 403 saying I don't have storage.objects.get access to a bucket?

That error is an IAM rejection: your account lacks permission on that bucket or on the project around it, so the request never gets far. If the bucket belongs to someone else, ask the owner to grant you a role that includes object read access. Test a bucket you own. If that one opens fine, permissions are your problem, not the service.

My project got suspended after a declined card. Does that show up here?

No. Billing trouble sits with your account rather than with the service, so report levels stay flat while every API call in your project fails. Open the billing section of the console to see the card status and the payment failure message, then update the payment method. Access returns shortly after the payment clears.
For your site

Put the Google Cloud status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

Google Cloud status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/google-cloud/"><img src="https://isitdownrightnow.app/badge/google-cloud.svg" alt="Google Cloud status" height="20"></a>
Markdown, for README files
[![Google Cloud status](https://isitdownrightnow.app/badge/google-cloud.svg)](https://isitdownrightnow.app/services/google-cloud/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Google Cloud

The status on this page comes from user-submitted problem reports for Google Cloud, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Google Cloud, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Google Cloud's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.

Elsewhere

Check other services