Ingestion and processing delay

What to do

• Check whether you use Iterable Journey Processing, Journey Processing, Journey Processing, User Updates and 5 more. 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 22m it lasted.

  Anything that failed between 2026-03-25 19:00 UTC and 2026-03-25 19:22 UTC may need a replay.

• Subscribe to Iterable's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=iterable works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Iterable 3

1. investigatingMar 25, 2026, 7: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

   provider

2. monitoringMar 25, 2026, 7:17 PM UTC

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

   provider

3. resolvedMar 25, 2026, 7:22 PM UTC

   This 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.