Courier: Delayed message delivery

What to do

Check whether you use Courier API. 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 8h 38m it lasted.
Anything that failed between 2024-02-19 17:12 UTC and 2024-02-20 01:51 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.

investigatingFeb 19, 2024, 5:12 PM UTC
We are currently investigating an issue causing delayed message delivery for some small percentage of requests processed by Courier.
provider
identifiedFeb 19, 2024, 5:17 PM UTC
The issue has been identified and a fix is being tested and implemented.
provider
monitoringFeb 19, 2024, 6:55 PM UTC
A fix has been implemented and the Courier Engineering team is monitoring system health.
provider
resolvedFeb 20, 2024, 1:51 AM UTC
The incident has been resolved.
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 2024-02-20 01:51 UTC. For Courier's live state, see https://down.guide/courier.

How long did it last?

8h 38m, from 2024-02-19 17:12 UTC to 2024-02-20 01:51 UTC, by the times Courier posted.

What was affected?

Courier named API.

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.