Courier: Courier Send and Message Event Slowdown

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 36m it lasted.
Anything that failed between 2025-02-13 22:32 UTC and 2025-02-13 23:09 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.

identifiedFeb 13, 2025, 10:32 PM UTC
The Courier team has identified a slowdown in sending notifications. This issue has been identified by our team and is closely monitoring. We do not expect any messages to drop. We will continue to monitor and update accordingly.
provider
monitoringFeb 13, 2025, 10:51 PM UTC
Our team has identified a bottleneck in our system caused by timeouts on our sendworker. Our exponential backoff has caught up and messages are starting to go through.
provider
resolvedFeb 13, 2025, 11:09 PM UTC
The team has identified the issue related to network connections on AWS which resulted in a backup of messages on our pipeline. Messages are flowing through as expected, and the stream has caught up.
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 2025-02-13 23:09 UTC. For Courier's live state, see https://down.guide/courier.

How long did it last?

36m, from 2025-02-13 22:32 UTC to 2025-02-13 23:09 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.