PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Amazon Web Services is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Amazon Web Services. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Amazon Web Services issues today?

As of Oct 3, 2026 08:27 UTC, 0 users had reported issues with Amazon Web Services in the previous 24 hours.

How can I report a Amazon Web Services outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Cloud Infrastructure

Is Amazon Web Services down right now?

NormalOfficial status last polled Oct 3, 2026 07:38 UTCaws.amazon.com Official status page

Amazon Web Services cloud infrastructure, console, compute, storage, networking, and managed service availability.

Are you on the Amazon Web Services team and see something inaccurate? Report it to us. We respond within one business day.

Is Amazon Web Services down right now?

No. Amazon Web Services has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 3, 2026 08:27 UTC

Normal

Amazon Web Services is operating normally

As of Oct 3, 2026 08:27 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 22, 2026 02:56 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Amazon Web Services.

Incident days

No recorded incident

3h 6m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Amazon Web Services. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

3h 6m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Amazon Web Services: vendor-reported incident on September 21 (tracked 3h 6m)

Sep 21, 11:50 PM → Sep 22, 02:56 AM · 3h 6m · high

Amazon Web Services reported an incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3h 6m, from Mon, 21 Sep 2026 23:50:35 GMT to Tue, 22 Sep 2026 02:56:52 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration

3h 6m

tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

Sep 21, 11:50 PM
The vendor reported an incident on its own status page; PulseWatch began tracking it
Sep 21, 11:50 PM
Status updated: possible issue
Sep 22, 02:56 AM
PulseWatch closed the incident

Official updates

Sep 21, 11:50 PM
Amazon Web Services reported the incident on its status page.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.57%

90-day uptime

98.8%

Calculated from Amazon Web Services's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

Amazon Web Services: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/21/2026, 11:50:35 PM · 3h 6m

11:50 PM02:56 AM

Detection9/21/2026, 11:50:35 PM · 11d ago

Detected — high severity

ResolvedMedium