- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2025-10-13 16:19 UTC and 2025-10-13 16:19 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 1
- resolved
Courier experienced a slowdown in message delivery with Mailgun providers around 2AM PST. Our monitoring systems caught the spike in the bottleneck, which eventually stabilized. Our infrastructure team is actively monitoring.
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-d5d54be0c8
Is Courier still down?
No, this incident was resolved 2025-10-13 16:19 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
0m, from 2025-10-13 16:19 UTC to 2025-10-13 16:19 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.