Resolved after 53 minutes, affecting API, on February 11, 2025.
The send stream has caught up, all messages have been sent and the issue appears to be fully resolved.
Affected components
Update timeline
- identified Feb 11, 2025, 10:15 PM UTC
The Courier team has identified a slowdown in our pipeline. The queue has backed up but no messages have been dropped at the moment. We will continue to update as we monitor our pipeline.
- monitoring Feb 11, 2025, 10:34 PM UTC
The team has identified the cause of message sends and slowdowns to be related to an AWS service. Messages that were stuck in a queued state are slowly passing through. The team will continue to monitor and update.
- resolved Feb 11, 2025, 11:08 PM UTC
The send stream has caught up, all messages have been sent and the issue appears to be fully resolved.
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