- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
What to do
Check whether you use Courier in eu. 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 6h 34m it lasted.
Anything that failed between 2025-05-16 14:28 UTC and 2025-05-16 21:02 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
- investigating
We are currently investigating an issue where EU workspace notifications appear to remain in the “queued” state.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
The issue has been resolved. The root cause was purely a logging issue, notifications were still sent but showing up in logs as queued. All logs have been rehydrated
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-0a344ac403
Is Courier still down?
No, this incident was resolved 2025-05-16 21:02 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
6h 34m, from 2025-05-16 14:28 UTC to 2025-05-16 21:02 UTC, by the times Courier posted.
What was affected?
Courier named in eu.
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.