- Level
- confirmed
- Worst impact
- Degraded
- Components
- Global Proof Sends
- Down Index
- 19of 100
What to do
Check whether you use Iterable Global Proof 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 2h 32m it lasted.
Anything that failed between 2026-03-16 16:18 UTC and 2026-03-16 18:50 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
We have been alerted to an issue where proofs sends are not being sent as expected as of 9:00 am PT. Iterable Engineers are actively investigating the issue. Next update by 11:00 am PT or sooner.
provider
- monitoring
The engineering team has implemented a fix and proofs are now successfully sending. We will continue to monitor. Next update at 12:00 PST or earlier.
provider
- resolved
This incident has been 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-746e7c4234
Is Iterable still down?
No, this incident was resolved 2026-03-16 18:50 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
2h 32m, from 2026-03-16 16:18 UTC to 2026-03-16 18:50 UTC, by the times Iterable posted.
What was affected?
Iterable named Global Proof 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.