- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Global Web Application
- Regions
- eu, us
What to do
Check whether you use Iterable Global Web Application in eu, us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 11m it lasted.
Anything that failed between 2026-02-24 18:18 UTC and 2026-02-24 18:30 UTC may need a replay.Subscribe to Iterable's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=iterable works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Iterable 3
- investigating
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.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-61f6b363f4
Is Iterable still down?
No, this incident was resolved 2026-02-24 18:30 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
11m, from 2026-02-24 18:18 UTC to 2026-02-24 18:30 UTC, by the times Iterable posted.
What was affected?
Iterable named Global Web Application in eu, us.
What caused it?
Iterable hasn't published a root cause. If it does, it shows here.
Where does this come from?
Iterable's official status page, https://status.iterable.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.