Skip to content
Amazon S3 logo

Cloud Infrastructure

Is Amazon S3 down right now?

UnknownOfficial status last polled Sep 7, 2026 14:24 UTCaws.amazon.com/s3Official status page

AWS Simple Storage Service - object storage

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

Is Amazon S3 down right now?

Unknown. Amazon S3 does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-09-26 could not be acquired.

Status as of Sep 26, 2026 12:21 UTC

Unknown

Amazon S3: status unknown

As of Sep 26, 2026 12:21 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

May 4, 2026 01:33 UTC

Trend

0/15m

Monitoring

Coverage gap

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 S3.

0

Incident days

30

No recorded incident

0 min

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 S3. Hover a day for detail.

Aug 28Sep 2Sep 7Sep 12Sep 17Sep 2201234

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

0

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

12:15 PM03:45 PM07:15 PM10:45 PM02:15 AM05:45 AM09:15 AM00.751.52.253baseline 2

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Amazon S3 outage on May 4 — 19-minute disruption

May 4, 01:13 AM → May 4, 01:33 AM · 19 minutes · medium

On May 4, 2026, Amazon S3 experienced a service disruption. This incident, which was detected through user reports and third-party monitoring, lasted for approximately 19 minutes. The issue was resolved at 01:33 UTC.

Peak reports
8
in 15 min
Total reports
0
during outage
Duration
19 minutes
until recovery

Impact

The disruption to Amazon S3 was detected through user reports, with a peak of 8 reports observed within a 15-minute period. These reports indicated general service unavailability. No specific issue types or geographic regions were predominantly identified among the user reports received during the incident.

Outage timeline

  1. May 4, 01:13 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 4, 01:15 AM

    Peak of 0 reports in 15 minutes (baseline 2.0)

  3. May 4, 01:33 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 01:13 AM

    Amazon S3 status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Amazon S3 is unknown, so there is no incident history to measure and no uptime figure is shown.

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.

500 characters left

Be the first to post a report.

Incident timeline

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

Full history →
ResolvedMedium

Amazon S3 incident correlated across 1 signal group: official/vendor.

5/4/2026, 1:13:04 AM · 19 min

01:13 AM01:33 AM
Detection5/4/2026, 1:13:04 AM · 4mo ago

Detected — medium severity

Amazon S3 incident correlated across 1 signal group: official/vendor.

ResolvedMedium

Amazon S3 incident correlated across 1 signal group: official/vendor.

5/1/2026, 2:13:02 AM · 19 min

02:13 AM02:33 AM
Detection5/1/2026, 2:13:02 AM · 4mo ago

Detected — medium severity

Amazon S3 incident correlated across 1 signal group: official/vendor.

ResolvedMedium

Amazon S3 incident correlated across 1 signal group: official/vendor.

4/30/2026, 5:13:05 AM · 20 min

05:13 AM05:33 AM
Detection4/30/2026, 5:13:05 AM · 4mo ago

Detected — medium severity

Amazon S3 incident correlated across 1 signal group: official/vendor.

ResolvedHigh

Amazon S3: grouped 7 related Website down alerts into one incident to reduce noise.

4/29/2026, 9:13:36 PM · 29 min

09:13 PM09:43 PM
Detection4/29/2026, 9:13:36 PM · 4mo ago

Detected — high severity

Amazon S3: grouped 7 related Website down alerts into one incident to reduce noise.

ResolvedMedium

Amazon S3 incident correlated across 1 signal group: official/vendor.

4/29/2026, 12:43:02 PM · 20 min

12:43 PM01:03 PM
Detection4/29/2026, 12:43:02 PM · 4mo ago

Detected — medium severity

Amazon S3 incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Amazon S3 enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Unknown
Monitoring
A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-09-26 could not be acquired.
Coverage
Reachability and crowd signals only; not independently verifiable
Reports (24h)
0
Baseline / hour
8
Open threshold
3x

Official site

aws.amazon.com/s3