- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 29of 100
What to do
Check whether your product depends on Courier. 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 2h 16m it lasted.
Anything that failed between 2023-06-13 19:13 UTC and 2023-06-13 21:28 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 5
- investigating
The engineering team is currently investing and working with the support team of our provider infrastructure.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
The extent of the outage with our service provider continues to increase. The team is closely monitoring.
provider
- monitoring
Systems should be returning to a normal operating state. Our engineering team will continue to monitor.
provider
- resolved
Services have been fully restored
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-9872f3efa6
Is Courier still down?
No, this incident was resolved 2023-06-13 21:28 UTC. For Courier's live state, see https://down.guide/providers/courier.
How long did it last?
2h 16m, from 2023-06-13 19:13 UTC to 2023-06-13 21:28 UTC, by the times Courier posted.
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.