Iterable incident

Iterable Application Issues in US Datacenter

Critical Resolved View vendor source →

Iterable experienced a critical incident on July 16, 2026 affecting Global Web Application and Global API Success and 1 more component, lasting 39m. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2026, 09:27 AM UTC
Resolved
Jul 16, 2026, 10:07 AM UTC
Duration
39m
Detected by Pingoru
Jul 16, 2026, 09:27 AM UTC

Affected components

Global Web ApplicationGlobal API SuccessGlobal LinksGlobal System WebhooksGlobal Partner WebhooksGlobal Analytics ProcessingGlobal CatalogGlobal API IngestionGlobal Campaign SendsGlobal Proof Sends

Update timeline

  1. investigating Jul 16, 2026, 09:27 AM UTC

    We are currently investigating an issue impacting the main Iterable application in the US region.

  2. identified Jul 16, 2026, 09:41 AM UTC

    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.

  3. identified Jul 16, 2026, 09:43 AM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Jul 16, 2026, 10:07 AM UTC

    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.