Google Cloud

cloud.google.com

live

Is Google Cloud down right now?

Q: Is Google Cloud down right now?

Check two places: the reports on this page, and status.cloud.google.com, which shows every product by region. Open the Asia Pacific tab for Mumbai and Delhi. If the dashboard shows no broad incident, Personalized Service Health in your console lists events that touch your own projects.

Q: Why is SSH to my Google Cloud VM not working?

Click Troubleshoot when the SSH-in-browser connection fails, or run gcloud compute ssh with the --troubleshoot flag. The tool checks your IAM permissions, the VM's network connection, whether the VM is running, and the SSH port in the VPC settings.

Google Cloud is working

Responding normally and no problems reported. If you still can't get on, it's likely your connection or app. Try the steps below.

Reports·1h: 0
Server: 200 OK
Response: 0.6s
Last checked: 6 hours ago

Answer: No Google Cloud issues reported in the last 24 hours, and it responded normally at our last check on 24 Oct 2026, 4:00 AM IST.

Report an issue

Our automated check runs from one or more locations and may miss in-app problems; reports come from users across India. We only call something "down" when users confirm it too. Here's how we check.

Not working for you? Report it

Takes 5 seconds, no login needed.

Last 24 hours: 0 reports.

About Google Cloud

For businesses and developers, Google Cloud, also called Google Cloud Platform or GCP, runs compute, storage, databases, Kubernetes, BigQuery and AI services. It has two cloud regions in India: Mumbai (asia-south1) and Delhi (asia-south2).

Its Service Health dashboard at status.cloud.google.com lists each product by region, so a fault in one region shows up there while the others stay available.

71-day history

healthy reports issues outage

We checked 84 times over the last 71 days — healthy on 65 days. It typically responds in about 0.6s.

71d ago 47d 24d today

Response time · daily average slowest day 0.8s

Dashed line is its usual 0.6s, measured over the last 14 days. Gaps are days with no timing data.

15 Aug no data

16 Aug no data

17 Aug checked, healthy

18 Aug checked, healthy

19 Aug no data

20 Aug checked, healthy

21 Aug no data

22 Aug checked, healthy

23 Aug no data

24 Aug checked, healthy

25 Aug no data

26 Aug checked, healthy

27 Aug checked, healthy

28 Aug checked, healthy

29 Aug checked, healthy

30 Aug checked, healthy

31 Aug checked, healthy

1 Sep checked, healthy

2 Sep checked, healthy

3 Sep checked, healthy

4 Sep checked, healthy

5 Sep checked, healthy avg 0.6s

6 Sep checked, healthy avg 0.6s

7 Sep checked, healthy avg 0.7s

8 Sep checked, healthy avg 0.7s

9 Sep checked, healthy avg 0.6s

10 Sep checked, healthy avg 0.6s

11 Sep checked, healthy avg 0.6s

12 Sep checked, healthy avg 0.6s

13 Sep checked, healthy avg 0.6s

14 Sep checked, healthy avg 0.6s

15 Sep checked, healthy avg 0.6s

16 Sep checked, healthy avg 0.6s

17 Sep checked, healthy avg 0.6s

18 Sep checked, healthy avg 0.6s

19 Sep checked, healthy avg 0.6s

20 Sep checked, healthy avg 0.6s

21 Sep checked, healthy avg 0.6s

22 Sep checked, healthy avg 0.8s

23 Sep checked, healthy avg 0.7s

24 Sep checked, healthy avg 0.7s

25 Sep checked, healthy avg 0.7s

26 Sep checked, healthy avg 0.7s

27 Sep checked, healthy avg 0.7s

28 Sep checked, healthy avg 0.6s

29 Sep checked, healthy avg 0.6s

30 Sep checked, healthy avg 0.6s

1 Oct checked, healthy avg 0.6s

2 Oct checked, healthy avg 0.6s

3 Oct checked, healthy avg 0.6s

4 Oct checked, healthy avg 0.6s

5 Oct checked, healthy avg 0.8s

6 Oct checked, healthy avg 0.7s

7 Oct checked, healthy avg 0.6s

8 Oct checked, healthy avg 0.7s

9 Oct checked, healthy avg 0.6s

10 Oct checked, healthy avg 0.6s

11 Oct checked, healthy avg 0.6s

12 Oct checked, healthy avg 0.6s

13 Oct checked, healthy avg 0.6s

14 Oct checked, healthy avg 0.6s

15 Oct checked, healthy avg 0.7s

16 Oct checked, healthy avg 0.7s

17 Oct checked, healthy avg 0.6s

18 Oct checked, healthy avg 0.7s

19 Oct checked, healthy avg 0.7s

20 Oct 1 report avg 0.7s

21 Oct checked, healthy avg 0.7s

22 Oct checked, healthy avg 0.6s

23 Oct checked, healthy avg 0.7s

24 Oct checked, healthy avg 0.6s

If Google Cloud isn't working

Check the Service Health dashboard Find your product and region on status.cloud.google.com. Mumbai is asia-south1 and Delhi is asia-south2.
See if other Google Cloud users report it Reports from many users at once point to Google Cloud's side rather than your project.
Check your billing status A declined payment can stop your services. Open Billing in the console and clear any balance due.
Run the SSH troubleshooter After a failed SSH connection, click Troubleshoot to test permissions, network and the VM itself.
Retry after a short wait For a brief error, wait and try once more instead of retrying again and again.

Other ways to access Google Cloud

Fail over to another region If your setup runs in both Mumbai and Delhi, send traffic to the region that is still available.
Turn on incident alerts Personalized Service Health in the console can send custom alerts for incidents that affect your projects.
Pay manually if auto-pay fails A manual payment by UPI or card keeps services running while you sort out a declined automatic payment.
Keep a fallback for critical traffic If you run a second cloud or a backup host, route the most important traffic there until Google Cloud recovers.
Billing and support routes Free billing help, paid support plans and India payment options are on the Google Cloud helpline page.

Official channels during an outage: X · Facebook · Instagram · YouTube · LinkedIn · Website

Questions

Check two places: the reports on this page, and status.cloud.google.com, which shows every product by region. Open the Asia Pacific tab for Mumbai and Delhi. If the dashboard shows no broad incident, Personalized Service Health in your console lists events that touch your own projects.

Look first for an incident against your product and region on the Service Health dashboard. A fault can hit one region while the rest stay available. If nothing is posted, check your billing, because Google Cloud may stop running your services when a payment is declined.

For new accounts in India, RBI rules can block automatic card payments: the card may not support them, or the amount may be over the RBI limit. The error reads 'Your card does not support automatic recurring payments'. Make a manual payment, add a different card, or pay through a local reseller.

Open the Payment overview for your billing account in the console and click Make a payment. Choose Pay with UPI, then scan the QR code in your UPI app. You need an Indian billing address, an Indian bank account and INR billing. Google's UPI guide says adding UPI as a payment method first needs a prepayment, typically 500 to 1000 rupees.

Click Troubleshoot when the SSH-in-browser connection fails, or run gcloud compute ssh with the --troubleshoot flag. The tool checks your IAM permissions, the VM's network connection, whether the VM is running, and the SSH port in the VPC settings.

The Free Trial needs a credit card or other payment method at sign-up, and some banks need the account verified before it starts. It gives $300 of credit for 90 days. The trial ends when 90 days pass or the credit runs out, whichever comes first.

status.cloud.google.com par Asia Pacific tab kholiye aur Mumbai ya Delhi region dekhiye. Wahan incident hai to Google ke fix ka intezaar kijiye. Incident nahi hai to console me billing ka payment status ek baar check kar lijiye.

Yes, tap Download on the status card at the top to save a server down image showing Google Cloud's current status, the last checked time, and how many users are reporting problems.