Resolved after 6 hours 19 minutes, affecting API, on April 30, 2025.
The team is still working through the reprocessing for impacted messages. Confirmation of all impacted messages reprocessed will be updated here.
Affected components
Update timeline
- identified Apr 30, 2025, 10:39 PM UTC
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 Apr 30, 2025, 10:47 PM UTC
The reverted changes will land in production in around one hour. The team will investigate the impact and handle message retries accordingly.
- monitoring Apr 30, 2025, 11:26 PM UTC
Fix has landed and the team is monitoring progress. Messages sent to AWS SES are sending normally. The team will reprocess impacted messages.
- monitoring May 01, 2025, 01:06 AM UTC
The team is still working through the reprocessing for impacted messages. Confirmation of all impacted messages reprocessed will be updated here.
- resolved May 01, 2025, 04:58 AM UTC
All impacted messages have been reprocessed.
Your product runs on more than Courier
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services