- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 27of 100
What to do
Check whether you use Courier API. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 4h it lasted.
Anything that failed between 2024-04-03 19:56 UTC and 2024-04-05 00:05 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
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
Issue has been fixed and automations are now being invoked. Automation logs might not reflect correct state - we're working on fixing it.
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-4f0cd9226f
Is Courier still down?
No, this incident was resolved 2024-04-05 00:05 UTC. For Courier's live state, see https://down.guide/providers/courier.
How long did it last?
1d 4h, from 2024-04-03 19:56 UTC to 2024-04-05 00:05 UTC, by the times Courier posted.
What was affected?
Courier named API.
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.