Ingestion Delays

What to do

• Check whether you use Iterable Global API Ingestion. 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 1h 58m it lasted.

  Anything that failed between 2025-06-12 19:17 UTC and 2025-06-12 21:16 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 4

1. identifiedJun 12, 2025, 7: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

   provider

2. identifiedJun 12, 2025, 7: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

   provider

3. monitoringJun 12, 2025, 8: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

   provider

4. resolvedJun 12, 2025, 9:16 PM UTC

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

   provider

Corrections

None so far.

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