- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 33of 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 11h 1m it lasted.
Anything that failed between 2023-11-02 15:58 UTC and 2023-11-03 02:59 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
We are currently investigating an issue that is affecting send times for some messages.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been deployed to Courier's production systems. The engineering team will continue to monitor as operations return to normal state.
provider
- resolved
System is back to a healthy state.
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-c18d8886ae
Is Courier still down?
No, this incident was resolved 2023-11-03 02:59 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
11h 1m, from 2023-11-02 15:58 UTC to 2023-11-03 02:59 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.