Skip to main content
AWS logo

Is AWS Down?

No — AWS is up

Reachable from all 18 checked regions

Average response time: 275ms

Last checked · checks run every 30 minutes

Official status page: https://health.aws.amazon.com/health/status

AWS uptime

100%
Last 7 days
99.99%
Last 30 days
99.99%
Last 90 days
319ms
Avg response, 30 days

Measured from multiple regions every 30 minutes. Percentages count only checks that returned an availability answer — 29 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

19-day clean streak
Jul 25: no data
Jul 26: 100.00% uptime, 404 checks
Jul 27: 99.89% uptime, 910 checks
Jul 28: 100.00% uptime, 915 checks
Jul 29: 100.00% uptime, 871 checks
Jul 30: 100.00% uptime, 857 checks
Jul 31: 100.00% uptime, 954 checks
Aug 1: 100.00% uptime, 839 checks
Aug 2: 100.00% uptime, 833 checks
Aug 3: 99.89% uptime, 891 checks
Aug 4: 99.90% uptime, 956 checks
Aug 5: 100.00% uptime, 962 checks
Aug 6: 100.00% uptime, 949 checks
Aug 7: 100.00% uptime, 861 checks
Aug 8: 100.00% uptime, 897 checks
Aug 9: 100.00% uptime, 878 checks
Aug 10: 100.00% uptime, 827 checks
Aug 11: 100.00% uptime, 880 checks
Aug 12: 100.00% uptime, 882 checks
Aug 13: 100.00% uptime, 908 checks
Aug 14: 100.00% uptime, 882 checks
Aug 15: 100.00% uptime, 859 checks
Aug 16: 100.00% uptime, 877 checks
Aug 17: 100.00% uptime, 824 checks
Aug 18: 100.00% uptime, 932 checks
Aug 19: 100.00% uptime, 932 checks
Aug 20: 100.00% uptime, 1009 checks
Aug 21: 100.00% uptime, 851 checks
Aug 22: 100.00% uptime, 862 checks
Aug 23: 100.00% uptime, 810 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
170ms
DNS 1ms TCP 1ms TLS 11ms TTFB 165ms
arn
298ms
DNS 0ms TCP 0ms TLS 2ms TTFB 191ms
bom
524ms
DNS 0ms TCP 1ms TLS 4ms TTFB 292ms
cdg
226ms
DNS 0ms TCP 1ms TLS 3ms TTFB 145ms
dfw
96ms
DNS 0ms TCP 1ms TLS 4ms TTFB 89ms
ewr
73ms
DNS 1ms TCP 1ms TLS 4ms TTFB 61ms
fra
158ms
DNS 0ms TCP 1ms TLS 3ms TTFB 151ms
gru
309ms
DNS 0ms TCP 3ms TLS 8ms TTFB 197ms
iad
75ms
DNS 1ms TCP 2ms TLS 4ms TTFB 60ms
jnb
317ms
DNS 0ms TCP 0ms TLS 2ms TTFB 310ms
lax
110ms
DNS 0ms TCP 2ms TLS 5ms TTFB 88ms
lhr
342ms
DNS 0ms TCP 4ms TLS 3ms TTFB 188ms
nrt
798ms
DNS 3ms TCP 3ms TLS 8ms TTFB 310ms
ord
95ms
DNS 0ms TCP 2ms TLS 3ms TTFB 81ms
sin
247ms
DNS 0ms TCP 2ms TLS 3ms TTFB 234ms
sjc
108ms
DNS 0ms TCP 2ms TLS 8ms TTFB 89ms
syd
888ms
DNS 0ms TCP 0ms TLS 3ms TTFB 192ms
yyz
120ms
DNS 0ms TCP 8ms TLS 9ms TTFB 89ms

What AWS does

Amazon Web Services is the world's largest cloud computing platform, providing over 200 services including compute, storage, databases, and machine learning. AWS powers a significant portion of the internet, hosting everything from small startups to major enterprises like Netflix, Airbnb, and NASA. Its global infrastructure spans dozens of regions and availability zones.

What an outage looks like

AWS outages can manifest in many ways depending on the affected service. Common symptoms include websites returning 500 errors, apps failing to load, API timeouts, and inability to access S3-hosted files or images. If core services like EC2 or Lambda are affected, entire applications may become unreachable.

What to do about it

Check health.aws.amazon.com for the AWS Service Health Dashboard, which shows per-service and per-region status. Identify which specific AWS service is affected and whether it's in your region. If you use multi-region deployments, consider failing over to a healthy region while the incident is being resolved.

Is it down for everyone, or just you?

If this page says AWS is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

AWS outage FAQ

How can I tell which AWS service is causing my issue?
The AWS Service Health Dashboard at health.aws.amazon.com shows status for every service in every region. You can also check your AWS Personal Health Dashboard in the AWS Console, which shows events specifically affecting your account and resources.
Does an AWS outage mean the entire internet is down?
No, AWS outages are almost always limited to specific services in specific regions. Even during major incidents, most AWS regions and services continue operating normally. However, because so many websites rely on AWS, a regional outage can affect a large number of popular sites simultaneously.
How often does AWS go down?
Individual AWS services maintain very high availability, typically 99.99% or better. However, with over 200 services across dozens of regions, some component is experiencing degradation on any given day. Major outages affecting core services like EC2 or S3 in a full region are rare, occurring a few times per year.
What is the difference between an AWS region outage and a service outage?
A service outage affects one specific AWS service (like S3 or Lambda) potentially across multiple regions. A regional outage affects multiple services within a single geographic region. Regional outages are more disruptive to applications hosted in that region but don't affect workloads in other regions.
Will AWS compensate me for downtime?
AWS offers service credits through their SLA if uptime falls below guaranteed thresholds. Each service has its own SLA, typically guaranteeing 99.99% monthly uptime. You need to submit a credit request through the AWS Support Center within 30 days of the incident.

How we measure this

  • We request AWS's public endpoint every 30 minutes from Fly.io regions across six continents — 18 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where AWS publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when AWS goes down

This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required