- 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 4m it lasted.
Anything that failed between 2024-07-29 22:03 UTC and 2024-07-29 23:07 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
- investigating
The Courier team has identified an issue impacting Automation services, which has resulted in degraded performance. An underlying issue was identified at around 10:30 PST and a fix was released at 11:00 PST. We are monitoring the automation worker for any leads.
provider
- monitoring
The team has identified the issue and is closely monitoring. Failed steps will continue to be retried with exponential backoff. Automations should recover, and all affected automations should execute after a delay of up to 15 minutes once the problem is resolved
provider
- resolved
Automations have stabilized.
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-b4e81a3d5a
Is Courier still down?
No, this incident was resolved 2024-07-29 23:07 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
1h 4m, from 2024-07-29 22:03 UTC to 2024-07-29 23:07 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.