- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 2h 2m it lasted.
Anything that failed between 2025-07-03 14:27 UTC and 2025-07-03 16: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
Around 2:16 AM PDT, we detected delays on journey processing. Current impact to our platform is stuck users and slow email sends, we are confirming other impact. Our team is actively working to resolve this as soon as possible. Next update will be provided at 8:30am PDT.
provider
- monitoring
We have deployed a fix to production at 7:30 AM PDT. Engineering continues to monitor effectiveness of the fix.
provider
- resolved
This incident is resolved and the backlog of processing has recovered. After further analysis engineering has provided an update that journey recovery started 6:30 to 7AM PST.
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-14870c7d73
Is Iterable still down?
No, this incident was resolved 2025-07-03 16:29 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
2h 2m, from 2025-07-03 14:27 UTC to 2025-07-03 16: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.