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.
1 year uptime
100.000%
365 of 365 days clean · 0m total downtime
Embed this badge
Live status pill for AWS SES. Updates automatically — no maintenance, no API key.
PREVIEW
Script tag
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
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>
Markdown / SVG
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/aws-ses)
Direct badge URL
Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/aws-ses/badge.svg
Frequently Asked Questions
›Is AWS SES currently down?
AWS 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.
›When did AWS SES last have an outage?
AWS SES has not had a resolved incident in the past 12 months on the surfaces CheckUpstream monitors.
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.
›How do I monitor AWS SES in production?
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).
›How does CheckUpstream track AWS SES?
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.