CheckUpstream has measured AWS SES at 100.000% uptime over the last 90 days and 100.000% over the last 12 months. No incidents have been recorded for AWS SES in the past 12 months. Status signals are polled from AWS SES's official status feed, alongside independent probes and community reports.
90 days uptime
100.000%
90 of 90 days clean · 0m total downtime
Live status pill for AWS SES. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=aws-ses"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/aws-ses" style="border:0;width:260px;height:44px" loading="lazy" title="AWS SES status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/aws-ses)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/aws-ses/badge.svgAWS SES is currently Operational. CheckUpstream tracks AWS SES in real-time across the official status page, RSS / Atom feeds, and community telemetry — refresh this page for the latest reading.
AWS SES has not had a resolved incident in the past 12 months on the surfaces CheckUpstream monitors.
Looking for the live "is AWS SES down" view? See the AWS SES Status page.
No incidents recorded for this service.
40signals across 2 sources
Synthetic probes 38 · active_probe 2
AWS SES's 30-day customer-perceived uptime is 100.000%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
Sign up to CheckUpstream and add AWS SES 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 SES'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.