Changes / Iterable / Iterable Application Issues in US Datacenter
Iterable: Critical incident: Iterable Application Issues in US Datacenter
Summary
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.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Iterable Application Issues in US Datacenter
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-07-16 09:27 UTC
Before: not present
After: 2026-07-16 10:07 UTC
Before: not present
After: Global Analytics Processing, Global API Ingestion, Global API Success, Global Campaign Sends, Global Catalog, Global Journey Processing, Global Links, Global Partner Webhooks, Global Proof Sends, Global System Webhooks, Global Web Application
Before: not present
After: We are currently investigating an issue impacting the main Iterable application in the US region.
Before: not present
After: Iterable engineering has identified the issue and is currently deployed a fix across the US environment. We are starting to see successful logins on the Iterable application.
Before: not present
After: We are continuing to work on a fix for this issue.
Before: not present
After: The issues with the Iterable application and API are now resolved and all sends and journeys that may have been delayed during the impact window have now been processed. Please reach out to Support if you continue to experience any issues.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Iterable Application Issues in US Datacenter (this change) 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 |