- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 19of 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 25m it lasted.
Anything that failed between 2025-02-18 14:22 UTC and 2025-02-18 14:47 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 identified a delay in message processing and event updating. The pipeline queue for message delivery has normalized, however significant slowdowns in message events are still processing.
provider
- monitoring
We're monitoring our processing pipeline as messages are flowing normally. There is a slight delay in event processing which will also impact outbound webhooks.
provider
- resolved
Message sends are flowing normally, and events are caught up without delays.
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-42d09aa636
Is Courier still down?
No, this incident was resolved 2025-02-18 14:47 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
25m, from 2025-02-18 14:22 UTC to 2025-02-18 14:47 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.