Changes / Iterable / app.iterable.com was unavailable in the US region, returning 502 Bad Gateway errors to users.
Iterable: Major incident: app.iterable.com was unavailable in the US region, returning 502 Bad Gateway errors to users.
Summary
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.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: app.iterable.com was unavailable in the US region, returning 502 Bad Gateway errors to users.
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-02-24 18:18 UTC
Before: not present
After: 2026-02-24 18:30 UTC
Before: not present
After: Global Web Application
Before: not present
After: We are currently investigating an issue where users could not access app.iterable.com and received 502 Bad Gateway errors. EU users were not affected.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: Service has fully recovered and all traffic has been restored to app.iterable.com in the US region. The incident lasted from 9:50 am to 10:15 am Pacific Time, impacting both web and API access with elevated 502, 503, and 504 errors. EU region was unaffected.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: app.iterable.com was unavailable in the US region, returning 502 Bad Gateway errors to users. (this change) 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 |