AWS

aws.amazon.com

live

Is AWS down right now?

Q: How do I check which AWS service or region is down?

Open the AWS Health Dashboard. Open and recent issues lists each problem with its service, region and timed updates, and Your account health shows events that touch your own resources.

AWS 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.7s
Last checked: 7 hours ago

Answer: No AWS issues reported in the last 24 hours, and it responded normally at our last check on 24 Oct 2026, 2:59 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 AWS

Many websites and apps run on Amazon Web Services (AWS), Amazon's cloud platform for servers, storage, databases and AI services. Its Indian company is Amazon Web Services India Private Limited, and its two Indian regions are Mumbai (ap-south-1) and Hyderabad (ap-south-2).

An AWS problem is usually one service in one region. The AWS Health Dashboard lists open issues by service and region, and every app built on that service in that region can fail at the same time.

71-day history

healthy reports issues outage

We checked 107 times over the last 71 days — healthy on 66 days. It typically responds in about 0.7s.

71d ago 47d 24d today

Response time · daily average slowest day 1.3s

Dashed line is its usual 0.7s, 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 checked, healthy

20 Aug checked, healthy

21 Aug no data

22 Aug checked, healthy

23 Aug checked, healthy

24 Aug no data

25 Aug checked, healthy

26 Aug no data

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.3s

6 Sep checked, healthy avg 0.3s

7 Sep checked, healthy avg 0.4s

8 Sep checked, healthy avg 0.6s

9 Sep checked, healthy avg 0.3s

10 Sep checked, healthy avg 0.6s

11 Sep checked, healthy avg 0.3s

12 Sep checked, healthy avg 0.8s

13 Sep checked, healthy avg 0.3s

14 Sep checked, healthy avg 0.3s

15 Sep checked, healthy avg 0.4s

16 Sep checked, healthy avg 0.6s

17 Sep checked, healthy avg 0.4s

18 Sep checked, healthy avg 0.8s

19 Sep checked, healthy avg 0.8s

20 Sep checked, healthy avg 0.5s

21 Sep checked, healthy avg 1.3s

22 Sep checked, healthy avg 0.4s

23 Sep checked, healthy avg 0.3s

24 Sep checked, healthy avg 0.5s

25 Sep checked, healthy avg 0.6s

26 Sep checked, healthy avg 0.4s

27 Sep checked, healthy avg 0.8s

28 Sep checked, healthy avg 0.4s

29 Sep checked, healthy avg 0.5s

30 Sep checked, healthy avg 0.5s

1 Oct 1 report avg 0.6s

2 Oct checked, healthy avg 0.4s

3 Oct checked, healthy avg 0.3s

4 Oct checked, healthy avg 0.3s

5 Oct checked, healthy avg 1.3s

6 Oct checked, healthy avg 0.4s

7 Oct checked, healthy avg 0.5s

8 Oct checked, healthy avg 0.8s

9 Oct checked, healthy avg 0.4s

10 Oct checked, healthy avg 0.7s

11 Oct checked, healthy avg 0.4s

12 Oct checked, healthy avg 0.6s

13 Oct checked, healthy avg 0.8s

14 Oct checked, healthy avg 0.7s

15 Oct checked, healthy avg 0.7s

16 Oct checked, healthy avg 0.8s

17 Oct checked, healthy avg 0.7s

18 Oct checked, healthy avg 0.7s

19 Oct checked, healthy avg 0.7s

20 Oct checked, healthy avg 0.7s

21 Oct checked, healthy avg 0.7s

22 Oct checked, healthy avg 0.8s

23 Oct checked, healthy avg 0.7s

24 Oct checked, healthy avg 0.7s

If AWS isn't working

Check the AWS Health Dashboard It lists open issues by service and region, with timed updates from AWS.
Match the region Most incidents hit one region. Check whether your resources are in Mumbai (ap-south-1), Hyderabad (ap-south-2) or somewhere else.
Retry with backoff For throttling or transient errors, retry after a short, growing wait instead of hammering the service.
Clear cookies for a console sign-in loop If the browser blocks sign-in, clear its cache and cookies or use some other browser.
See if others are reporting it Many users in India reporting AWS here at the same moment points to a platform problem, not your code.

Other ways to access AWS

Fail over to another region If a whole AWS region is failing and your architecture spans more than one, move traffic to a region that is healthy.
Use the CLI or SDK if only the console fails The AWS CLI and SDKs call the service APIs directly, so they can often still work while the console web pages will not load.
Route critical paths to a backup provider If you run multi-cloud or keep a fallback provider, sending critical traffic there keeps things up during the outage.
Open a support case Raise a case in the AWS Support Center and choose web, chat or a phone callback. Every route is on the verified AWS helpline page.

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

Questions

Many reports from India here at the same time mean an AWS service is failing for everyone. Match them against the AWS Health Dashboard, which lists open issues by service and region. Few reports and a clean dashboard point to your own setup.

Often one service in one region is failing, not all of AWS. The Health Dashboard names both, for example Amazon EC2 in N. Virginia. If your workload runs in Mumbai (ap-south-1) or Hyderabad (ap-south-2) and neither shows an issue, check your own configuration, credentials and quotas.

Those apps run on AWS. When a service they depend on fails in their region, they fail with it, even though their own names never mention AWS. Service history on the Health Dashboard shows which AWS services were hit and when.

Clear the browser cache and cookies, or try another browser, first. The root user signs in with the account email and password; an IAM user needs the credentials the account administrator gave. A lost or broken MFA device has its own support form, and the account support form reaches AWS without signing in.

Open the AWS Health Dashboard. Open and recent issues lists each problem with its service, region and timed updates, and Your account health shows events that touch your own resources.

Check that the charge really is from AWS, then whether a colleague, a contractor or an old Free Tier account left resources running. If you still cannot trace it, AWS's billing or account support form works even without an account. If someone used your card without permission, dispute it with the card issuer.

AWS Health Dashboard par Open and recent issues dekhein, wahan service aur region ka naam likha hota hai. Mumbai ya Hyderabad region mein koi issue na ho aur yahan reports kam hon, to apni configuration, credentials aur quota check karein.

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

Platform outage or account issue on AWS? See the verified AWS support contacts and the official status page.

[email protected]

AWS · 24x7

Full helpline