- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 21of 100
What to do
Check whether you use Courier API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 53m it lasted.
Anything that failed between 2025-02-11 22:15 UTC and 2025-02-11 23:08 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 3
- identified
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.
provider
- monitoring
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.
provider
- resolved
The send stream has caught up, all messages have been sent and the issue appears to be fully resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a2706043b2
Is Courier still down?
No, this incident was resolved 2025-02-11 23:08 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
53m, from 2025-02-11 22:15 UTC to 2025-02-11 23:08 UTC, by the times Courier posted.
What was affected?
Courier named API.
What caused it?
Courier hasn't published a root cause. If it does, it shows here.
Where does this come from?
Courier's official status page, https://status.courier.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.