Courier Inbox FetchMessages Connectivity Issues

What to do

• Check whether you use Courier Courier Inbox. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 9h 47m it lasted.

  Anything that failed between 2024-10-10 16:46 UTC and 2024-10-11 02:33 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 8

1. investigatingOct 10, 2024, 3:38 PM UTC

   The Courier Team is investigating an issue related to Inbox fetching messages in the component.

   provider

2. identifiedOct 10, 2024, 4:30 PM UTC

   The team has identified the issue and will be rolling out a fix. The team will reprocess the impacted messages that were not fetched.

   provider

3. monitoringOct 10, 2024, 4:46 PM UTC

   Inbox connectivity for fetching messages has been reestablished. The team is monitoring closely, and working on retroactively processing impacted messages to Inbox

   provider

4. monitoringOct 10, 2024, 5:50 PM UTC

   We are continuing to gather a list of impacted messages to backfill impacted Inbox components.

   provider

5. monitoringOct 10, 2024, 6:06 PM UTC

   We are continuing to monitor for any further issues.

   provider

6. monitoringOct 10, 2024, 7:07 PM UTC

   The team has gathered impacted messages and is running tests before a release.

   provider

7. monitoringOct 10, 2024, 8:51 PM UTC

   The team has initiated backlogging the impacted Inbox messages.

   provider

8. resolvedOct 11, 2024, 2:33 AM UTC

   Inbox connectivity issues resolved.

   provider

Corrections

None so far.

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