Courier incident

Delay in Message Sends and Processing

Minor Resolved View vendor source →

Courier experienced a minor incident on February 11, 2025 affecting API, lasting 53m. The incident has been resolved; the full update timeline is below.

Started
Feb 11, 2025, 10:15 PM UTC
Resolved
Feb 11, 2025, 11:08 PM UTC
Duration
53m
Detected by Pingoru
Feb 11, 2025, 10:15 PM UTC

Affected components

API

Update timeline

  1. identified Feb 11, 2025, 10:15 PM UTC

    The Courier team has identified a slowdown in our pipeline. The queue has backed up but no messages have been dropped at the moment. We will continue to update as we monitor our pipeline.

  2. monitoring Feb 11, 2025, 10:34 PM UTC

    The team has identified the cause of message sends and slowdowns to be related to an AWS service. Messages that were stuck in a queued state are slowly passing through. The team will continue to monitor and update.

  3. resolved Feb 11, 2025, 11:08 PM UTC

    The send stream has caught up, all messages have been sent and the issue appears to be fully resolved.