Is Amazon Web Services down?
Right now
No. Amazon Web Services is operational.
No incidents reported.
Read from health.aws.amazon.com · every 300s
For agents
proceed
Proceed.
GET upbutler.com/status/aws/status.agent.json
MCP: upstream_status {"service":"aws"}
AWS Health public events for the regions most products run in. us-east-1 incidents reach far beyond AWS customers, because much of the internet depends on it.
What Amazon Web Services reports
Operational
Taken as is from Amazon Web Services's own AWS Health public events. Incident titles and component names below are theirs. Narrowed to what concerns Amazon Web Services.
Open health.aws.amazon.comUpButler's independent probe
There is no keyless endpoint of Amazon Web Services that says anything useful, so UpButler does not probe it. To check your own Amazon Web Services account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Amazon Web Services components
8 operational
- us-east-1Operational
- us-east-2Operational
- us-west-2Operational
- eu-west-1Operational
- eu-central-1Operational
- ap-southeast-1Operational
- ap-northeast-1Operational
- globalOperational
Amazon Web Services incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Amazon Web Services publishes for 90 days from the day it starts tracking a service.
Tell your outage from Amazon Web Services's
Declare that your project depends on Amazon Web Services. When one of your monitors fails while Amazon Web Services has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- awscurl -s https://upbutler.com/status/aws/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "aws",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Amazon Web Services down right now?
- No. As of 2026-10-10 05:06 UTC, Amazon Web Services is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Amazon Web Services's own AWS Health public events at https://health.aws.amazon.com/health/status. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Amazon Web Services's words. Their page covers more than this page shows; it is narrowed to the parts that concern Amazon Web Services.
- How can my agent or app check Amazon Web Services status?
- Fetch https://upbutler.com/status/aws/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"aws"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Amazon Web Services's?
- Add "aws" to the dependencies of your UpButler workspace. When one of your monitors fails while Amazon Web Services has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in cloud and edge
UpButler is not affiliated with Amazon Web Services. Status and incident text belong to Amazon Web Services and are read from their public status source; the probe result is UpButler's own measurement.