- Level
- confirmed
- Worst impact
- Degraded
- Components
- Global System Webhooks
- Down Index
- 23of 100
What to do
Check whether you use Iterable Global System Webhooks. 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 22h 35m it lasted.
Anything that failed between 2024-10-25 21:00 UTC and 2024-10-26 19:35 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
The code fix for the slowness of System webhooks is deployed. Currently the queue is depleting. This could take several hours to deplete the backlog completely. During this time the performance will be degraded. Next update at 6pm PST.
provider
- monitoring
System webhook backlog is depleted and the incident is resolved.
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-3111fe04cc
Is Iterable still down?
No, this incident was resolved 2024-10-26 19:35 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
22h 35m, from 2024-10-25 21:00 UTC to 2024-10-26 19:35 UTC, by the times Iterable posted.
What was affected?
Iterable named Global System Webhooks.
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.