- Level
- confirmed
- Worst impact
- Degraded
- Components
- Global API Success
- Down Index
- 17of 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 56m it lasted.
Anything that failed between 2026-09-22 19:02 UTC and 2026-09-22 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 3
- investigating
We are currently investigating an issue leading to slowness and timeouts across all API user update endpoints beginning at 2:45 PM EDT. Next update at 3:15 PM EDT
provider
- monitoring
We are continuing to investigate the issue but are seeing positive signs of recovery. API endpoints for user updates are back to normal success rates. Next update at 3:45 PM EDT or sooner.
provider
- resolved
All API issues are now resolved and the user update endpoints are fully operational. If you continue to experience any issues, please contact 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-fd61ed273f
Is Iterable still down?
No, this incident was resolved 2026-09-22 19:58 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
56m, from 2026-09-22 19:02 UTC to 2026-09-22 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.