Send Pipeline Latency

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 1h 57m it lasted.

  Anything that failed between 2026-06-18 20:11 UTC and 2026-06-18 22: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.

Updates from Courier 5

1. identifiedJun 18, 2026, 8:11 PM UTC

   The team has identified a regression causing send requests to be stuck in a queued state. We have initiated a rollback to quickly resolve the issue. More updates to follow

   provider

2. identifiedJun 18, 2026, 8:35 PM UTC

   The rollback deploy will land in about 30 minutes.

   provider

3. identifiedJun 18, 2026, 9:31 PM UTC

   The team has identified that the most recent deployment was not the cause of the regression. The team is still working on identifying the root cause. Messages will not be dropped, and they will be processed once the fix is out.

   provider

4. monitoringJun 18, 2026, 9:53 PM UTC

   Messages are being processed while our pipeline continues to process enqueued messages.

   provider

5. resolvedJun 18, 2026, 10:09 PM UTC

   Send pipeline has resolved and enqueued messages are now sending properly.

   provider

Corrections

None so far.

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