- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 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 1h it lasted.
Anything that failed between 2025-09-22 07:24 UTC and 2025-09-22 08:24 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
- identified
We are currently experiencing a service disruption with our catalog service, which may prevent some customers from sending messages that use templates with catalog data. Messages that do not use catalog data are not impacted. We've identified the root cause and are actively working on a fix. Please note that no messages have been lost. Our system will automatically retry all failed sends once the service has recovered. We will provide another update in 30 minutes, or sooner if the issue is resolved. We apologize for the inconvenience and thank you for your patience.
provider
- identified
We have started rolling out the fix to individual machines and are seeing some of our messaging capabilities recover. Some customers may still have a delay in sends that use templates with catalog data, and ingestion delays for updating catalog data. We are continuing to apply the fix across all affected systems and will monitor the situation closely. No messages have been lost, and our system will automatically retry all failed sends once the service has fully recovered. We will provide another update in 30 minutes, or sooner if the issue is resolved. We appreciate your continued patience.
provider
- resolved
The issue with our catalog service has been fully resolved, and all services are now operating normally. Any delayed sends and catalog updates are being processed currently. Messages that were queued during the disruption will be automatically retried and delivered.
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-3ef23e1cee
Is Iterable still down?
No, this incident was resolved 2025-09-22 08:24 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
1h, from 2025-09-22 07:24 UTC to 2025-09-22 08:24 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.