Iterable change history

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.

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.

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.

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.

Iterable reported a major outage affecting its web application, global APIs, sends and Journeys, causing errors, timeouts and delays from 2025-10-20 13:15 UTC to 2025-10-20 21:54 UTC (8 h 39 min). A third-party provider experienced instability and applied regional mitigations. Queued sends cleared, and lingering AI and datasharing latency was resolved.

Iterable’s Auth service experienced a major degradation affecting access to app.iterable.com from 2025-08-08 23:44 UTC to 2025-08-09 00:29 UTC, lasting 44 min. Iterable addressed an issue in its service and confirmed login recovery; the API was unaffected, and campaigns and journeys continued processing as expected.

Iterable reported a major C120 outage starting 2025-04-23 06:50 UTC, lasting 40 h 26 min and resolved at 2025-04-24 23:17 UTC. A cluster formation problem caused query failures, campaign impacts and ingestion lag; users triggering journeys via custom events, system events or profile updates did not enter journeys. Engineering restored data and cut over to Cluster 141.

Iterable reported a critical Global API Ingestion delay on Clusters 100 and above from 2025-03-14 16:56 UTC to 2025-03-14 21:13 UTC, lasting 4 h 16 min. User updates, list uploads, user deletion and event processing were delayed; email sends and journey processing could also be affected. Engineering deployed a fix and confirmed recovery; no data was dropped.

Iterable reported a major Global Web Application incident affecting fetching, creating and saving Journeys, causing delays or unexpected behavior. It started at 2025-03-07 09:57 UTC and was resolved at 2025-03-07 18:35 UTC, lasting 8 h 38 min. A fix was deployed by 10:32 UTC, restoring normal Journey function; Iterable later confirmed no further journey-edit errors.

Iterable reported a major incident affecting Global API Success, with intermittent partial API outages lasting several minutes. The incident started at 2025-01-07 19:56 UTC and was resolved at 2025-01-07 22:10 UTC, lasting 2 h 13 min. Engineers implemented a fix and reported no further API outages.

Iterable reported major delays ingesting new users into Event-Triggered Journeys from 2024-12-31 14:29 UTC to 2024-12-31 18:25 UTC, lasting 3 h 55 min. Errors in workflow-entrance-trigger pods caused a backlog; Iterable updated the service and scaled up pods, then confirmed the backlog was drained. Scheduled Journeys and API Triggered Journeys were unaffected.

Iterable reported a major incident involving API and web application errors, with delays to sends and journey processing. It started at 2024-11-24 18:16 UTC and was resolved at 2024-11-25 17:09 UTC, lasting 22 h 52 min; engineering applied mitigations and reported recovery in the web application and API endpoints.

Iterable reported a major incident affecting Global Campaign Sends and Global Proof Sends, with email send errors and campaign send skips linked to a third-party ESP’s API. It started at 2024-10-15 16:06 UTC and resolved at 2024-10-15 21:32 UTC, lasting 5 h 25 min. The vendor released a fix, and all affected messages were successfully processed.