Companies / Iterable / changes
Iterable change history
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Iterable Application Issues in US Datacenter Iterable reported a critical US-region application and API outage starting 2026-07-16 09:27 UTC, resolved at 2026-07-16 10:07 UTC (39 min). Engineering deployed a fix across the US environment; successful logins resumed, and all sends and journeys that may have been delayed were processed by resolution. | Major incident | |
| Critical incident: Iterable Web Application Outage - US and EU Regions Iterable reported a critical US and EU web application outage from 2026-05-12 23:31 UTC to 2026-05-13 00:08 UTC, lasting 37 min. Customers could not log in and experienced slow page loads; email sends, API traffic, webhooks, and journeys remained unaffected. Engineering deployed a fix in both regions and confirmed normal service. | Major incident | |
| Major incident: Email send delays for some US-hosted SparkPost traffic Iterable reported a major degradation in Global Campaign Sends: US-hosted customers using SparkPost experienced email delays from elevated 5xx errors and Transmissions API latency. It started at 2026-02-24 19:51 UTC and resolved at 2026-02-24 19:52 UTC, lasting 1 minute. EU-hosted traffic and other ESPs were unaffected; SparkPost’s API issue was resolved. | Major incident | |
| Major incident: app.iterable.com was unavailable in the US region, returning 502 Bad Gateway errors to users. Iterable reported a major US-region outage of app.iterable.com affecting web and API access with elevated 502, 503, and 504 errors; EU users were unaffected. It started at 2026-02-24 18:18 UTC and was resolved at 2026-02-24 18:30 UTC (computed duration: 11 min), after a fix was implemented and traffic fully restored. | Major incident | |
| Major incident: Platform Impact – Third-Party Vendor Disruption (Regional) | Major incident | |
| Major incident: Iterable Auth service degraded | Major incident | |
| Major incident: Queries to data stored on C120 cluster are failing | Major incident | |
| Critical incident: Ingestion Delay on Clusters 100 and Above | Major incident | |
| Major incident: Journeys are having issues fetching, creating and saving journeys. | Major incident | |
| Major incident: Intermittent API errors | Major incident | |
| Major incident: Event-Triggered Journeys Delays Ingesting New Users | Major incident | |
| Major incident: Web Application Errors | Major incident | |
| Major incident: Issues impacting Email Sending | Major incident |