Is Amazon Web Services down?

aws.amazon.com · Cloud & infrastructure · official status page

Amazon Web Services has recorded 100.0% uptime over the last 5 days, with no outage. It answers our checks in 182 ms on average.

No problems detected

Amazon Web Services answered our last automated check normally, 11 minutes ago. If it is not working for you, the problem is most likely local - Your connection, your DNS resolver, a cached page, or an extension.

Last checked 210 ms · HTTP 200
Uptime, 30 days 100.0% 0 seconds down
Reports, 24h 0 baseline still forming
Recorded outages 0 full history

Amazon Web Services problem reports in the last 24 hours

Counted in 15-minute buckets from reports submitted on this site. This is a user signal - A tall bar means people are complaining, not that our check failed.

No reports in the last 24 hours.

If Amazon Web Services is not working for you, tell us and the chart starts here.

Response time from our automated checks

The last 24 checks of https://aws.amazon.com/ from our network. Bar height is the response time; the tallest bar is the slowest.

22 Sep 2026, 21:47 UTC slowest 278 ms 23 Sep 2026, 05:27 UTC
  • Answered normally
  • Slow to answer
  • No usable answer

Having a problem with Amazon Web Services?

Tell us what is not working. Reports go straight onto the 24-hour chart above and help other people see a problem before any company admits to one. 0 reports in the last 24 hours.

What is not working?

No account needed. We store a one-way hash of your address to stop the same connection reporting repeatedly - Never the address itself, and never your name. One report per service every 30 minutes.

About Amazon Web Services outages

AWS is the single biggest source of correlated internet outages. A fault in us-east-1, its oldest and busiest region in Northern Virginia, has repeatedly taken down services with no obvious relationship to each other - Smart doorbells, airline check-in, project trackers and streaming apps all at once - Because so many companies run their control planes there.

The pattern to recognise is breadth: If a dozen unrelated apps start failing in the same few minutes, suspect a shared provider rather than a dozen coincidences. Within AWS, the services that cause the widest blast radius are IAM and STS (authentication), DynamoDB, S3, and the internal DNS layer, because almost everything else depends on them. AWS reports incidents on its Health Dashboard, which historically has been slow to turn red; account-specific impact appears faster in the personal health dashboard inside the console than on the public page.

What to do if Amazon Web Services is not working for you

Is it them or you?

Our last check reached aws.amazon.com normally, from a different network, resolver and route than yours. If it is broken for you, the fault is most likely local or too narrow for a single probe to see. Run the check again now to confirm.

The first thing worth trying

Notice the pattern before you troubleshoot. Three unrelated sites failing together is not three coincidences. Stop checking your own equipment.

How cloud & infrastructure services typically fail

Many unrelated services fail at once, in the same minutes, for the same people. Errors are inconsistent - some sites time out, others return a gateway error, others load partially - because each one fails at whatever layer it depended on. The rest of the steps, and why this category breaks the way it does, are on our cloud & infrastructure status page, with more background in how a single provider takes out half the web.

Amazon Web Services measured against its peers

How it compares with other cloud & infrastructure services

Over the last 30 days Amazon Web Services ranks 1 of 9 cloud & infrastructure services we monitor, measured on recorded uptime. The category averages 100.0%, and Amazon Web Services sits at 100.0%. That is the best record in the group.

On speed, Amazon Web Services answers our checks in about 182 ms against a category average of 243 ms - Faster than its peers. Response time is not availability, but a service drifting well above its own normal is often the first sign of trouble.

What the last 24 checks looked like

Across the most recent 24 checks, the quickest response was 132 ms and the slowest 278 ms, against a 30-day average of 182 ms. The chart above plots each one, so a widening spread is visible before it becomes an outage.

All figures are our own measurements, taken every 20 minutes from one network. What that can and cannot see is set out in the methodology, and every cloud & infrastructure service is listed on the category page.

The server that answered Mostly hidden

IP address
13.33.67.120 and 11 others
Server
Hidden until you sign in
Powered by
Hidden until you sign in
Content type
Hidden until you sign in
Declared size
Hidden until you sign in
Transport and HSTS
Hidden until you sign in

Five more fields about the server behind aws.amazon.com.

Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.

Sign in to unlock

Read from our last sweep of aws.amazon.com, not requested when you opened this page.

Certificate Mostly hidden

Status
Valid
Issued to
Hidden until you sign in
Issued by
Hidden until you sign in
Valid from
Hidden until you sign in
Expires
Hidden until you sign in
Protocol and cipher
Hidden until you sign in

Who issued it, what it covers and exactly when it expires.

Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.

Sign in to unlock

An expired certificate stops browsers loading a site entirely while the server itself stays perfectly healthy, which is why we track it beside the uptime figure. Check it yourself.

Amazon Web Services status: Common questions

Is Amazon Web Services down right now?

Amazon Web Services is up and responding normally. This page is refreshed by an automated check that runs every 20 minutes from an independent network, and by reports from visitors.

Why can I not reach Amazon Web Services when you say it is up?

Because an outage can be partial. Our check runs from one network and asks for one page. Your problem may be regional, may affect only the mobile app, or may be local to your connection, DNS resolver or browser cache.

How reliable is Amazon Web Services?

Amazon Web Services has been reachable for 100.0% of the last 5 days we have measured, with 0 seconds of recorded downtime.

Does Amazon Web Services have an official status page?

Yes - Amazon Web Services publishes one at https://health.aws.amazon.com/health/status. It is the authoritative source for confirmed incidents, though official pages usually update after user reports have already peaked.

Amazon Web Services discussion

Useful comments say what broke, roughly where you are and roughly when it started - That is what turns a pile of complaints into something other people can act on. Links are shown as plain text and carry no SEO value, so there is nothing here worth spamming.

No comments yet. If Amazon Web Services is not working for you, be the first to say what you are seeing.