Courier: AWS SES Failures
Affected components: API
Timeline of updates
- identified
The Courier team has identified an issue with a recent deployment that is impacting AWS SES integrations. We have found the root cause and have reverted the changes. The team is gathering impact.
- identified
The reverted changes will land in production in around one hour. The team will investigate the impact and handle message retries accordingly.
- monitoring
Fix has landed and the team is monitoring progress. Messages sent to AWS SES are sending normally. The team will reprocess impacted messages.
- monitoring
The team is still working through the reprocessing for impacted messages. Confirmation of all impacted messages reprocessed will be updated here.
- resolved
All impacted messages have been reprocessed.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:33 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
878b1000acf5c0f2…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).