- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Iterable. 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 50m it lasted.
Anything that failed between 2026-04-16 10:09 UTC and 2026-04-16 10:59 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’re currently investigating an issue where Journey pages are not responding. Engineering is actively applying a fix and will continue investigating the root cause. Next update at 4:00 PM PST / 11:00 PM GMT.
provider
- monitoring
Journey pages are loading normally following the fix. Engineering will continue monitoring.
provider
- resolved
This incident has been resolved.
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-d7e013e99c
Is Iterable still down?
No, this incident was resolved 2026-04-16 10:59 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
50m, from 2026-04-16 10:09 UTC to 2026-04-16 10:59 UTC, by the times Iterable posted.
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.