Iterable incident

Ingestion Delays

Minor Resolved View vendor source →

Iterable experienced a minor incident on June 12, 2025 affecting Global API Ingestion, lasting 1h 58m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 07:17 PM UTC
Resolved
Jun 12, 2025, 09:16 PM UTC
Duration
1h 58m
Detected by Pingoru
Jun 12, 2025, 07:17 PM UTC

Affected components

Global API Ingestion

Update timeline

  1. identified Jun 12, 2025, 07:17 PM UTC

    Starting around 11:30 AM PT, Iterable Engineering detected a growing lag across clusters causing delays with user updates, list uploads, user deletion, and event processing. Engineering has identified the cause related to an upstream network provider and is working to remediate these delays. Next update at 1:00 PM PT or sooner

  2. identified Jun 12, 2025, 07:59 PM UTC

    We are still seeing ingestion lag across all clusters. No data is being dropped; however, there are delays in user updates, list uploads, user deletion, and event processing, which may also impact journey triggers. Next update at 2:00 PM PT or sooner

  3. monitoring Jun 12, 2025, 08:45 PM UTC

    We are seeing ingestion lag recovering across all clusters and catching up on the remaining backlog. The team is continuing to monitor. Next update at 2:15 PM PT or sooner

  4. resolved Jun 12, 2025, 09:16 PM UTC

    Ingestion lag has recovered across all clusters. This incident is now resolved.