CheckUpstream measured AWS SES at 99.988% availability across 8449 independent checks (3 regions · ses). 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 SES in the past 12 months. Status signals are polled from AWS SES's official status feed, alongside independent probes and community reports.
30 days measured availability how this is computed
99.988%
3 regions · ses · n=8449 · p95 667ms (30d)
Share of our own checks against AWS SES endpoints that returned AWS SES's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
AWS SES 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 SES
7d
100.000%
30d
100.000%
90d
100.000%
180d
100.000%
1y
100.000%
Downtime like this can be refundable
If you're a paying AWS SES customer, outages in these windows may count against AWS SES's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your AWS SES entitlement →Does AWS SES actually matter to you?
A AWS SES 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 SES status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/aws-ses)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
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.
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 Live status page.
AWS SES's 30-day measured availability is 99.988%, from CheckUpstream's own probes against AWS SES endpoints. It is the share of checks that returned the expected response, not a figure taken from AWS SES's status page.
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.