- Level
- confirmed
- Worst impact
- Degraded
- Components
- Global Web Application
- Down Index
- 23of 100
What to do
Check whether you use Iterable Global Web Application. 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 5d 5h it lasted.
Anything that failed between 2025-10-09 14:48 UTC and 2025-10-14 20:34 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 12
- investigating
Any visitor who entered a delay tile longer than 24hrs that received an exit match post 8:30 PM PST yesterday October 8th, with no subsequent updates to their exit rules may continue to experience incorrect journey exits until October 10th 8:30 PM PST. Any user receiving an exit rule update since then will not be impacted and will exit correctly. Overall this represented less than 1% of total users within Journeys with the final number being much lower due to many users in delays receiving exit rule updates since the beginning of the impact window which negated the issue. For those customers impacted the most our teams are reaching out to them to discuss next steps. We wil provide the next update before 10AM PT.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
The engineering team has successfully identified the root cause of this incident: a major infrastructure issue experienced by one of our key vendors. We are actively partnering with the vendor to ensure the issue is fully resolved and to prevent any future impacts to our services. Next Update: We will provide our next status update before 12:00 PM PT.
provider
- monitoring
The key vendor has confirmed the defect on their side and has taken steps to prevent recurrence. We will continue to closely monitor the affected systems. We will provide our next status update before 3:00 PM PT.
provider
- monitoring
There is no further recurrence of the infrastructure issue from our key vendor. We will continue to monitor the affected infrastructure for recurrence. Next Update: We will provide our next status update before 9:00 AM PT on October 10, 2025.
provider
- investigating
The fix applied by our key vendor did not work. The impact is that a limited amount of exit rule data was lost. We began observing a recurrence of the same limited data loss on October 10th, 2025, at 7:00 AM PST. We are working with the vendor to investigate further. Next Update: We will provide our next status update before 10:00 AM PT.
provider
- investigating
We worked with the vendor to fix this issue. The vendor recommended an approach to prevent additional data loss. We will apply the fix and monitor the affected systems for recurrence. Next Update: We will provide our next status update before 12:00 PM PT.
provider
- monitoring
We have successfully deployed the fix and will start monitoring for recurrences. Next Update: We will provide our next status update before 3:00 PM PT.
provider
- monitoring
There are no further recurrences after the fix was deployed today. We will continue to monitor the affected systems over the weekend.
provider
- monitoring
There were no recurrences observed from October 10th afternoon to October 13th morning. We will continue to monitor until the end of the day. Next Update: We will provide our next status update before 5:00 PM PT.
provider
- monitoring
There were no recurrences observed today. We will continue to monitor for recurrence. Next Update: We will provide our next status update before 12:00 PM PT tomorrow.
provider
- resolved
We have observed no recurrence since 10/10. The issue now is resolved. Please feel free to reach out to support for further questions.
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-4d7bd4492c
Is Iterable still down?
No, this incident was resolved 2025-10-14 20:34 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
5d 5h, from 2025-10-09 14:48 UTC to 2025-10-14 20:34 UTC, by the times Iterable posted.
What was affected?
Iterable named Global Web Application.
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.