Iterable: Delays processing user and event data on some clusters
Affected components: Cluster 101 - Email SendsCluster 101 - Journey ProcessingCluster 101 - List UpdatesCluster 101 - Push SendsCluster 101 - SMS SendsCluster 101 - User DeletionsCluster 101 - User UpdatesEmail SendsGlobal API IngestionJourney ProcessingList UpdatesPush SendsSMS SendsUser DeletionsUser Updates
Timeline of updates
- 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.
- 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.
- identified
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.
- 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.
- 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.
Changes Rewindex caught on this incident
- Incident updated: Delays processing user and event data on some clusters
- Incident updated: Delays processing user and event data on some clusters
- Incident updated: Delays processing user and event data on some clusters
- Incident updated: Delays processing user and event data on some clusters
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.iterable.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Iterable, started 2026-11-16 16:00 UTC, resolved after 4.2 h, 5 update(s); edited after publishing.
- Title
- Delays processing user and event data on some clusters
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/tvw5n88qvb9d
Iterable profileRecent Iterable incidentsAll outages on November 16, 2026Iterable in November 2026MarkdownJSON