Delays processing user and event data on some clusters

Incident Report for Iterable

Resolved

The issue causing delays in processing user profile and event updates has been resolved, and normal processing has resumed across the affected clusters. No data loss was reported. If you received an error when submitting a bulk user update API request, please retry that request. We apologize for the disruption and appreciate your patience.
Posted Nov 16, 2026 - 12:14 PST

Monitoring

We have applied a fix, and processing has returned to normal on all affected clusters except cluster 101. Cluster 101 is now processing again and working through its backlog of delayed updates, which will be processed automatically. We will keep cluster 101 marked as degraded until it has fully caught up, and we will post another update by 10:30 PT or sooner.
Posted Nov 16, 2026 - 09:35 PST

Update

Processing of user profile and event updates has returned to normal on all affected clusters except cluster 101. Updates on cluster 101 are still delayed, and our engineering team is working to restore normal processing there. Delayed updates on cluster 101 will be processed automatically once it catches up. We will post another update by 9:30 PT or sooner.
Posted Nov 16, 2026 - 08:55 PST

Identified

We have identified the cause of the processing delays and are rolling out a fix. Processing has already returned to normal on some affected clusters, and the remaining clusters are recovering as the fix is applied. Delayed updates will be processed automatically once each cluster has caught up. Some bulk user update API requests may have returned errors during this period; if you received errors, please retry those requests. We will post another update by 9:00 PT or sooner.
Posted Nov 16, 2026 - 08:41 PST

Investigating

Starting around 14:00 UTC we started seeing delays in processing user profile and event updates for customers on some clusters. Data sent to Iterable is being accepted but is taking longer than usual to appear on user profiles, and segments and journeys that rely on that data may also be delayed. No data has been lost. Our engineering team is actively investigating, and we will post another update within 60 minutes.
Posted Nov 16, 2026 - 08:00 PST
This incident affected: Cluster 101 (Email Sends, Journey Processing, Push Sends, SMS Sends, User Updates, List Updates, User Deletions) and Global API Ingestion.