CheckUpstream measured AWS S3 at 100.000% availability across 8493 independent checks (3 regions · s3). AWS publishes no catalogue of the services it reports on, so an incident reaches this page only when AWS names this product in the event itself. A quiet page here means AWS named no event for it — not that we have measured anything. No incidents have been recorded for AWS S3 in the past 12 months. Status signals are polled from AWS S3's official status feed, alongside independent probes and community reports.
90 days measured availability how this is computed
100.000%
3 regions · s3 · n=8493 · p95 690ms (30d)
Share of our own checks against AWS S3 endpoints that returned AWS S3's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
AWS S3 posted no incidents in this window. That is either a clean run or a communication policy — from outside, the two look identical.
Fewer incidents in the last 30 days than 55% of 232 tracked services.
Share of each window with no impact declared by AWS S3
7d
100.000%
30d
100.000%
90d
100.000%
180d
100.000%
1y
100.000%
Does AWS S3 actually matter to you?
A AWS S3 outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →No incidents recorded for this service.
Live AWS S3 status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/aws-s3)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
AWS S3 is currently Operational. CheckUpstream tracks AWS S3 in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
AWS S3 has not had a resolved incident in the past 12 months on the surfaces CheckUpstream monitors.
Looking for the live "is AWS S3 down" view? See the AWS S3 Live status page.
AWS S3's 30-day measured availability is 100.000%, from CheckUpstream's own probes against AWS S3 endpoints. It is the share of checks that returned the expected response, not a figure taken from AWS S3's status page.
Sign up to CheckUpstream and add AWS S3 to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll AWS S3's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.