- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 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 45m it lasted.
Anything that failed between 2025-08-08 23:44 UTC and 2025-08-09 00:29 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 seeing issues accessing app.iterable.com. We have identified an issue in one of our services and Engineering is working on a fix. Iterable API is not impacted. All campaigns and journeys are processing as expected. Next update will be by 5PM PDT.
provider
- monitoring
We have addressed the issue in our service and app.iterable.com is accessible again. Engineering is monitoring the situation. Next update will be at or before 5:30PM PDT.
provider
- resolved
Our login service has recovered and app.iterable.com is fully accessible. If you are still having issues, please reach out to support.
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-04511a1bbc
Is Iterable still down?
No, this incident was resolved 2025-08-09 00:29 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
45m, from 2025-08-08 23:44 UTC to 2025-08-09 00:29 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.