- Level
- confirmed
- Worst impact
- Degraded
- Components
- SMS Sends, Global Campaign Sends
- Down Index
- 21of 100
What to do
Check whether you use Iterable SMS Sends, Global Campaign Sends. 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 4h 55m it lasted.
Anything that failed between 2025-08-01 20:32 UTC and 2025-08-02 01:27 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 7
- investigating
We are currently investigating an increase in embedded Messaging skips, which appears to be impacting most customers. Other sends globally are not impacted. Our team is actively working to identify the root cause of this issue. Next Update: We will provide our next update by 2:00 PM PDT.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
The issue with embedded messages incorrectly being send skipped has been identified and the team is actively working to remediate it. We have confirmed that the impact is only to embedded messages triggered by Journeys. The aforementioned remediation should be completed shortly and we will continue to monitor that no further send skip issues occur once complete. Next update: We will provide our next update at 3:00 PM PDT.
provider
- identified
The send skip behavior for journey triggered embedded messages has been resolved. The team is still working on validating that the remediation has restored full functionality. Next update: We will provide our next update at 4:00 PM PDT.
provider
- identified
During the validation of the remediation, the team identified that another fix was necessary to fully restore the functionality of journey triggered embedded messages. They are working on testing and releasing the fix. Next update: We will provide our next update at 6:00 PM PDT.
provider
- identified
The additional fix has been tested successfully and deployment is in progress. This process will take another 15-30 minutes to rollout to all customers. This will fully restore functionality for journey triggered embedded messaging, which were the only sends impacted. Next up: Our next update will be at or before 7:00 PM PDT.
provider
- resolved
This incident has been resolved and functionality has been fully restored for journey triggered embedded messaging sends. If more information is needed, please reach out to support@iterable.com. This will be the final update.
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-7bd56beb3b
Is Iterable still down?
No, this incident was resolved 2025-08-02 01:27 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
4h 55m, from 2025-08-01 20:32 UTC to 2025-08-02 01:27 UTC, by the times Iterable posted.
What was affected?
Iterable named SMS Sends, Global Campaign Sends.
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.