Is AWS down right now?
HostTracker's monitoring network reached aws.amazon.com and completed a full check without errors. It has been up for 14d 9h.
Checking aws.amazon.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
Incident history
LAST 90 DAYSNo incidents recorded in the last 90 days.
About AWS outages
Written by the HostTracker monitoring team · updated from live probe data.
Amazon Web Services underpins a substantial share of the internet's backend infrastructure across dozens of regions and hundreds of distinct services (EC2, S3, RDS, Lambda, and more), so an AWS incident's visible impact depends entirely on which service and which region is affected - a single-region S3 issue can take down specific apps while leaving AWS-hosted competitors in other regions completely unaffected. This makes "is AWS down" a genuinely different question from "is my AWS-hosted app down": AWS itself is rarely globally down, but a regional or per-service incident can still fully outage any application that depends on that specific piece of infrastructure. Checking the reachability of your own AWS-hosted endpoints directly, alongside AWS's own regional health status, gives a much clearer picture than either alone.
Common causes of AWS downtime
Regional service disruptions affecting a specific AWS region (e.g. us-east-1) while other regions remain fully operational
Individual service incidents (S3, EC2, Lambda, RDS, DynamoDB, etc.) that can cascade into dependent services within the same region
Networking or DNS issues within AWS's backbone that affect connectivity between services or to the public internet
Capacity-related throttling during unusually high demand, degrading performance without a full outage
Not sure whether it's AWS or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 13 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests aws.amazon.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than AWS being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
Almost never - AWS operates dozens of independent regions and hundreds of distinct services, and a genuine simultaneous global outage across all of them is extremely rare. What's commonly reported as "AWS is down" is almost always a specific service (like S3 or EC2) having an incident in one or a handful of regions, which can still be severe because so many other companies' applications depend on that exact service/region combination - but it's a regional/service-scoped event, not the whole cloud going dark. Checking AWS's own per-region, per-service health status alongside your specific application's endpoints gives the accurate picture.
Start by testing your actual application's public endpoint from multiple independent locations - if it's unreachable or erroring, and you can also confirm AWS is reporting an incident in the specific region and service your app depends on, that's a strong signal the root cause is upstream at AWS. If AWS reports no incident in your region/service but your application is still down, the problem is more likely in your own application code, a recent deployment, a misconfiguration, or a dependency outside AWS entirely (a third-party API, DNS provider, or CDN). Comparing your own monitoring history against AWS's incident timeline is usually the fastest way to tell the two apart.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.