- Level
- confirmed
- Worst impact
- Degraded
- Components
- Automations
- Down Index
- 22of 100
What to do
Check whether you use Courier Automations. 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 1h 16m it lasted.
Anything that failed between 2024-06-27 23:24 UTC and 2024-06-28 00:40 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 2
- investigating
Automation delays are occurring due to a combination of data retrieval issues and system timeouts. The team is investigating .
provider
- resolved
This incident has been resolved, automation throughput has returned to normal levels.
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-a7c4214463
Is Courier still down?
No, this incident was resolved 2024-06-28 00:40 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
1h 16m, from 2024-06-27 23:24 UTC to 2024-06-28 00:40 UTC, by the times Courier posted.
What was affected?
Courier named Automations.
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.