AWS SES Failures

What to do

• Check whether you use Courier API. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 6h 20m it lasted.

  Anything that failed between 2025-04-30 22:39 UTC and 2025-05-01 04:58 UTC may need a replay.

• Subscribe to Courier's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=courier works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Courier 5

1. identifiedApr 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.

   provider

2. identifiedApr 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.

   provider

3. monitoringApr 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.

   provider

4. monitoringMay 1, 2025, 1:06 AM UTC

   The team is still working through the reprocessing for impacted messages. Confirmation of all impacted messages reprocessed will be updated here.

   provider

5. resolvedMay 1, 2025, 4:58 AM UTC

   All impacted messages have been reprocessed.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.