- Level
- confirmed
- Worst impact
- Degraded
- Components
- Global API Success
- Down Index
- 23of 100
What to do
Check whether you use Iterable Global API Success. 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 21h 53m it lasted.
Anything that failed between 2026-01-01 22:05 UTC and 2026-01-02 19:58 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 4
- investigating
API Update is experiencing timeouts starting at 11:00 AM PST. The Engineering team is investigating. Next update at 3:00 PM PST.
provider
- monitoring
API Update has recovered. The engineering team will continue to monitor—next update on January 2nd, at 9 AM PST.
provider
- monitoring
API Update is stable. The engineering team will continue to monitor. Next update at 12:00 PM PST.
provider
- resolved
The engineering team determined that the issue 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-6617da7a6b
Is Iterable still down?
No, this incident was resolved 2026-01-02 19:58 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
21h 53m, from 2026-01-01 22:05 UTC to 2026-01-02 19:58 UTC, by the times Iterable posted.
What was affected?
Iterable named Global API Success.
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.