Courier: Message Status Delays

What to do

Check whether you use Courier Web Application, 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 1h 5m it lasted.
Anything that failed between 2023-03-28 22:22 UTC and 2023-03-28 23:27 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.

identifiedMar 28, 2023, 10:22 PM UTC
We have identified an issue that is causing message status delays to be reflected. This will also result in delayed outbound webhook message delivery. A fix is being tested and deployed.
provider
monitoringMar 28, 2023, 10:59 PM UTC
A fix has been deployed and the engineering team is monitoring status
provider
resolvedMar 28, 2023, 11:27 PM UTC
System is back to being healthy and fully operational
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-03-28 23:27 UTC. For Courier's live state, see https://down.guide/courier.

How long did it last?

1h 5m, from 2023-03-28 22:22 UTC to 2023-03-28 23:27 UTC, by the times Courier posted.

What was affected?

Courier named Web Application, 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.