- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web Application, Automations
- Down Index
- 31of 100
What to do
Check whether you use Courier Web Application, Automations. 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 3d 3h it lasted.
Anything that failed between 2024-07-09 19:18 UTC and 2024-07-12 22:25 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
Courier Automation logs are currently experiencing a delay in showing up. The team is aware of this issue and is mitigating the root cause by relieving the bottleneck of incoming Automation requests.
provider
- resolved
This was a symptom of a previous automation issue, where a snowball effect caused a massive backlog of events. It took a long time for the Kinesis stream to catch up. We resolved the issue by temporarily increasing the stream shard count. The issue is now fully 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-275ce694b0
Is Courier still down?
No, this incident was resolved 2024-07-12 22:25 UTC. For Courier's live state, see https://down.guide/providers/courier.
How long did it last?
3d 3h, from 2024-07-09 19:18 UTC to 2024-07-12 22:25 UTC, by the times Courier posted.
What was affected?
Courier named Web Application, 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.