Courier: An incident with Courier's hosting infrastructure has been identified and is impacting access to service.

What to do

Check whether your product depends on Courier. 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 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.

investigatingJun 13, 2023, 7:13 PM UTC
The engineering team is currently investing and working with the support team of our provider infrastructure.
provider
investigatingJun 13, 2023, 7:13 PM UTC
We are continuing to investigate this issue.
provider
investigatingJun 13, 2023, 8:23 PM UTC
The extent of the outage with our service provider continues to increase. The team is closely monitoring.
provider
monitoringJun 13, 2023, 9:07 PM UTC
Systems should be returning to a normal operating state. Our engineering team will continue to monitor.
provider
resolvedJun 13, 2023, 9:28 PM UTC
Services have been fully restored
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Courier still down?

No, this incident was resolved 2023-06-13 21:28 UTC. For Courier's live state, see https://down.guide/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.