Ingestion Delays and API Failures on C18

What to do

• Check whether you use Iterable User Updates, List Uploads, User Deletions. 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 27m it lasted.

  Anything that failed between 2025-07-28 10:21 UTC and 2025-07-28 10:48 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. investigatingJul 28, 2025, 10:21 AM UTC

   Beginning at 2:30 AM PDT, Iterable Engineering detected an issue with our C18 clusters leading to delays on user updates, list uploads, user deletion, and event processing. Additionally, there were failures on API calls to endpoints such as event/track for a period of time. Next update at 3:45 AM PDT or sooner.

   provider

2. monitoringJul 28, 2025, 10:39 AM UTC

   Ingestion lag for C18 is recovering and success rates for all services are back to normal. We will continue to monitor the cluster until the ingestion backlog has fully cleared. Next update at 4:30 AM PDT or sooner.

   provider

3. monitoringJul 28, 2025, 10:39 AM UTC

   We are continuing to monitor for any further issues.

   provider

4. resolvedJul 28, 2025, 10:48 AM UTC

   The system has finished working on backlog of data and the data is caught up. All systems are operational and have no issues. Engineering will continue to monitor the cluster performance.

   provider

Corrections

None so far.

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