- Level
- confirmed
- Worst impact
- Major outage
- Components
- Web Application, API, Automations, Observability, Courier Inbox
- Down Index
- 59of 100
What to do
Check whether you use Courier Web Application, API, Automations, Observability and 1 more. 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 52m it lasted.
Anything that failed between 2025-10-20 09:19 UTC and 2025-10-20 10:11 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
- identified
An issue with our service provider, AWS, has impacted all Courier services. The engineering team is working on resolution.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
Service has been restored. Engineering is working through system review and will continue to monitor.
provider
- resolved
The 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-4b77c285ec
Is Courier still down?
No, this incident was resolved 2025-10-20 10:11 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
52m, from 2025-10-20 09:19 UTC to 2025-10-20 10:11 UTC, by the times Courier posted.
What was affected?
Courier named Web Application, API, Automations, Observability and 1 more.
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.