How we source & verify data

awsdown.com exists to be the fastest, most trustworthy answer to one question: is AWS down right now? Trust requires transparency — here is exactly where our data comes from and how we verify it.

One authoritative source

Every incident comes from the public AWS Health Dashboard — the same feed AWS uses to power health.aws.amazon.com. We do not invent, infer, or editorialize incidents.

Polled every 60 seconds

Our server checks the AWS feed once a minute and timestamps each incident with a "last verified" time so you always know how fresh the data is.

Verifiable evidence

Each incident links back to the official source and carries AWS’s own event reference (ARN) plus the verbatim, timestamped updates AWS published.

Independent & unaffiliated

awsdown.com is an independent monitor. We are not affiliated with, endorsed by, or operated by Amazon Web Services.

Our data source

We continuously read the public AWS Health Dashboard event feed — the canonical, AWS-published record of service events across every region. (AWS’s own legacy status endpoint redirects to it.) For each event we store the affected services and regions, the severity, and AWS’s full update timeline, verbatim.

Official AWS Health Dashboard

What the statuses mean

Operational: No reported incidents — the service is operating normally.
Degraded: A regional incident or minor issue is affecting the service. Most users are unaffected.
Partial Outage: A significant issue in a primary region (us-east-1) or global scope.
Major Outage: A critical issue in a primary/global scope with broad impact.
Maintenance: Planned maintenance is in progress.

Regional vs. global: AWS reports status per region. A service’s headline status here reflects global impact — incidents confined to a single region are shown as degraded (with the exact region on the incident), while issues in the primary us-east-1 region or global scope escalate to a full outage. This avoids overstating a localized event as a worldwide one.

Honest limitations

AWS does not offer a public real-time push stream; we poll the public feed every ~60 seconds, so there can be a short delay versus AWS’s own dashboard.
Historical incidents accumulate from the point we began monitoring; we don’t fabricate past events.
We track a curated set of major AWS services. Sub-services roll up to their parent.

See it in action on the live status dashboard or browse the incident history.