Space for ads
Checked every 5 minutes · How we measure this
As of 01:05 EDT on 22 Sep 2026, aws.amazon.com responded to our check in 905 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 9 minutes ago
The line is response time measured from our probe to aws.amazon.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
0 problem reports
AWS outage
DownBits detected an outage on AWS between 18 Sep 2026, 13:30 – 13:40 IST, lasting ongoing. Detected across 2 consecutive automated checks of aws.amazon.com.
Detected by DownBits probe
AWS is responding normally. Our last automated check of aws.amazon.com completed 9 minutes ago and succeeded in 905 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, AWS has been available 100.00% over 24 hours, 99.85% over 7 days, 99.86% over 30 days. We recorded 1 incident in the last 30 days.
AWS has averaged 1,083 ms across our successful checks in the past 24 hours, which is slower than ideal and may feel sluggish on a weak connection. Response time is measured from our probe to aws.amazon.com and does not include rendering time in your browser.
The most recent incident DownBits recorded for AWS began on 18 September 2026 at 13:30 IST and lasted 10 min. It was logged as outage. Detected by DownBits probe.
Our probe is reaching aws.amazon.com normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://aws.amazon.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than AWS. On Windows run ping aws.amazon.com and nslookup aws.amazon.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load aws.amazon.com in a private or incognito window. If it works there, clear cookies and site data for aws.amazon.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
