Is Amazon Web Services down right now?

No. Our checks are finding no problems with Amazon Web Services right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Amazon Web Services continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, can't connect, API errors, 5xx error pages, no response / timing out, high latency, DNS / site unreachable and slow or laggy. Those are the options the report button offers for Amazon Web Services, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Amazon Web Services specifically, AWS is regional by design and nearly every incident stays inside one region or even one availability zone. us-east-1 additionally hosts global control planes including parts of IAM and the console, so a problem there breaks things everywhere while the rest of AWS is fine. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Amazon Web Services, make the same API call against a different region. Succeeding there confirms the region rather than your credentials. Failing in every region usually means an expired session token or IAM change on your side, which returns errors that look like an outage. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Amazon Web Services's side. Specifically: do not fail resources over unless you have tested that failover before. A half-configured cross-region failover run for the first time during an incident reliably causes a second outage on top of the first. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Amazon Web Services does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe aws.amazon.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Amazon Web Services says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.aws.amazon.com, and it is linked further up this page. That is Amazon Web Services's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Amazon Web Services or aws.amazon.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Amazon Web Services's own support, not us.