- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web Application
- Down Index
- 21of 100
What to do
Check whether you use Courier Web Application. 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 49m it lasted.
Anything that failed between 2024-06-11 15:36 UTC and 2024-06-11 16:26 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
- investigating
There is an increased number of events in Courier's events log table causing delayed queued events to display. The team has upped the write capacity for these events and is waiting for the stream to stabilize.
provider
- identified
The Courier team has identified the issue with the events table and has upped the capacity until events stabilize.
provider
- monitoring
Events are slowly stabilizing and the team is monitoring.
provider
- resolved
Events log stream has 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-de2fab5c28
Is Courier still down?
No, this incident was resolved 2024-06-11 16:26 UTC. For Courier's live state, see https://down.guide/courier.
How long did it last?
49m, from 2024-06-11 15:36 UTC to 2024-06-11 16:26 UTC, by the times Courier posted.
What was affected?
Courier named Web Application.
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.