- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 26of 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 39m it lasted.
Anything that failed between 2023-07-21 18:02 UTC and 2023-07-21 18:41 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 4
- investigating
Courier has found an issue causing delay in messages being sent. We've identified the root cause and a fix is on its way to production, we'll follow up shortly with an update when the fix is live.
provider
- identified
The issue has been identified and a fix is on its way to production
provider
- monitoring
System looks healthy and we're monitoring closely.
provider
- resolved
This incident has been 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-ebabe212a5
Is Courier still down?
No, this incident was resolved 2023-07-21 18:41 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
39m, from 2023-07-21 18:02 UTC to 2023-07-21 18:41 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.