Iterable incident

Ingestion and processing delay

Minor Resolved View vendor source →

Iterable experienced a minor incident on March 25, 2026 affecting Journey Processing and Journey Processing and 1 more component, lasting 22m. The incident has been resolved; the full update timeline is below.

Started
Mar 25, 2026, 07:00 PM UTC
Resolved
Mar 25, 2026, 07:22 PM UTC
Duration
22m
Detected by Pingoru
Mar 25, 2026, 07:00 PM UTC

Affected components

Journey ProcessingJourney ProcessingJourney ProcessingUser UpdatesUser UpdatesUser UpdatesList UploadsList UploadsList Updates

Update timeline

  1. investigating Mar 25, 2026, 07:00 PM UTC

    Current status We have identified an issue in our ingestion service that can cause some updates to be delayed. Customer impact Some customers are seeing delays in list uploads and events appearing in Iterable, in some cases taking 30+ minutes to render. Clusters impacted 22,25,16 Rolled back to a previous stable version across all affected clusters and verified the deployments. We are monitoring ingestion lag and key metrics to confirm performance is stabilizing and that no new update loss is occurring. If you are experiencing delayed data visibility or suspect missing updates, please contact our Support team so we can review your specific projects as part of this incident. Next update 1pm PT

  2. monitoring Mar 25, 2026, 07:17 PM UTC

    We have caught up with ingestion. Currently monitoring our systems.

  3. resolved Mar 25, 2026, 07:22 PM UTC

    This incident has been resolved.