Courier incident

AWS SES Failures

Minor Resolved View vendor source →

Courier experienced a minor incident on April 30, 2025 affecting API, lasting 6h 19m. The incident has been resolved; the full update timeline is below.

Started
Apr 30, 2025, 10:39 PM UTC
Resolved
May 01, 2025, 04:58 AM UTC
Duration
6h 19m
Detected by Pingoru
Apr 30, 2025, 10:39 PM UTC

Affected components

API

Update timeline

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

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

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

  4. 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.

  5. resolved May 01, 2025, 04:58 AM UTC

    All impacted messages have been reprocessed.