- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 13of 100
What to do
Check whether your product depends on Courier. 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 10m it lasted.
Anything that failed between 2026-05-27 23:06 UTC and 2026-05-27 23:16 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
Slack has reported messaging, and app degredation on their platform that could be impacting deliverability of Slack messages. This is a downstream provider issue and can be monitored on Slack's statuspage: https://slack-status.com/
provider
- resolved
Please continue to monitor Slack's statuspage for any updates related to message deliverability: https://slack-status.com/
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-28449dd8d6
Is Courier still down?
No, this incident was resolved 2026-05-27 23:16 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
10m, from 2026-05-27 23:06 UTC to 2026-05-27 23:16 UTC, by the times Courier posted.
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.