- Level
- confirmed
- Worst impact
- Degraded
- Components
- Automations
- Down Index
- 22of 100
What to do
Check whether you use Courier Automations. 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 1h 16m it lasted.
Anything that failed between 2025-02-21 15:55 UTC and 2025-02-21 17:10 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 2
- monitoring
The Courier team has identified a slowdown in Segment event processing. There will be a slight delay for messages triggered by incoming Segment triggers. We estimate the queue to normalize soon and are monitoring.
provider
- resolved
Segment event processing stream has 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-3c239841c2
Is Courier still down?
No, this incident was resolved 2025-02-21 17:10 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
1h 16m, from 2025-02-21 15:55 UTC to 2025-02-21 17:10 UTC, by the times Courier posted.
What was affected?
Courier named Automations.
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.