Issue affecting sends

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 2h 40m it lasted.

  Anything that failed between 2023-05-11 17:23 UTC and 2023-05-11 20:04 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 4

1. investigatingMay 11, 2023, 5:23 PM UTC

   We are currently investigating an issue that appears to be affecting a percentage of messages being processed. In addition, customers may be receiving "NOT FOUND" errors for messages IDs that are affected when attempting to access them via logs or the API.

   provider

2. investigatingMay 11, 2023, 7:08 PM UTC

   We are continuing to investigate the issue. The team believes < that 8% of all messages to be impacted though further analysis is continuing. Out of an abundance of caution, the team has also ramped down rollout of any upgrades and features through our experimentation engine.

   provider

3. monitoringMay 11, 2023, 7:37 PM UTC

   A fix has been deployed. The team is continuing to monitor. Any affected messages will automatically be reprocessed. The team will continue to monitor the health of the platform.

   provider

4. resolvedMay 11, 2023, 8:04 PM UTC

   The incident has been resolved

   provider

Corrections

None so far.

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