- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Global API Success
- Down Index
- 29of 100
What to do
Check whether you use Iterable Global API Success. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 14m it lasted.
Anything that failed between 2025-01-07 19:56 UTC and 2025-01-07 22:10 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
Our on-call engineers are investigating intermittent partial API outages lasting several minutes over the past couple hours. Our monitoring and alerting first detected the issue near 8:53 am PST. Next update by 1PM PST.
provider
- monitoring
Our engineering team implemented a fix for the issue and have seen no further API outages. We are continuing to monitor the situation.
provider
- resolved
We have not seen further API outages since the last update. This incident is now 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-abb681ad78
Is Iterable still down?
No, this incident was resolved 2025-01-07 22:10 UTC. For Iterable's live state, see https://down.guide/providers/iterable.
How long did it last?
2h 14m, from 2025-01-07 19:56 UTC to 2025-01-07 22:10 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.