- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Iterable. 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 19h 46m it lasted.
Anything that failed between 2024-10-22 17:33 UTC and 2024-10-23 13:18 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
Errors with our Embedded Messaging API are not occurring any more. The engineering team remediated the issue by clearing the offending database requests that were queued up. This is a temporary fix. A permanent remediation with code fix is still in progress.
provider
- monitoring
Errors with our Embedded Messaging API are not occurring any more. A code fix has been deployed.
provider
- resolved
This issue has been fully resolved as of October 22nd at 5pm PST.
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-73abdd151c
Is Iterable still down?
No, this incident was resolved 2024-10-23 13:18 UTC. For Iterable's live state, see https://down.guide/providers/iterable.
How long did it last?
19h 46m, from 2024-10-22 17:33 UTC to 2024-10-23 13:18 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.