Is AWS Down Right Now?

The instant check tool above tests aws.amazon.com live from HostTracker's network of 300+ worldwide locations at once, rather than from 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.