- Level
- confirmed
- Worst impact
- Degraded
- Components
- Email Sends, Email Sends, Email Sends, Email Sends, Email Sends, Email Sends, Journey Processing, Journey Processing, Journey Processing, Journey Processing, Journey Processing, Journey Processing, User Updates, User Updates, User Updates, User Updates, User Updates, User Updates, List Uploads, List Uploads, List Uploads, List Updates, List Updates, List Updates, User Deletions, User Deletions, User Deletions, User Deletions, User Deletions, User Deletions
- Down Index
- 20of 100
What to do
Check whether you use Iterable Email Sends, Email Sends, Email Sends, Email Sends and 26 more. 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 6m it lasted.
Anything that failed between 2024-11-12 17:18 UTC and 2024-11-12 19:24 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
Starting at around 6:30 am PT, Iterable Engineers were notified that lag on our ingestion topics was growing on a subset of clusters. Customers on these impacted clusters could be experiencing delays with user updates, list uploads, user deletion, and event processing. Email sends and journey processing may see impact as well. Data is only being delayed. It is not being dropped. The engineering team is working to remediate these delays. Next update at 10:00 an PT or Sooner.
provider
- monitoring
The engineering team has identified the cause and remediated the delays on these subset of clusters. Most impacted ingestion topics have recovered and customers should start to see data being ingested normally again. We are still working through some backlog, so the team will continue to monitor to ensure that these delays don't recur. Next Update at 11:00 am PT or sooner?
provider
- resolved
Ingestion has returned to normal for all impacted clusters and this issue is now 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-df505ec237
Is Iterable still down?
No, this incident was resolved 2024-11-12 19:24 UTC. For Iterable's live state, see https://down.guide/iterable.
How long did it last?
2h 6m, from 2024-11-12 17:18 UTC to 2024-11-12 19:24 UTC, by the times Iterable posted.
What was affected?
Iterable named Email Sends, Email Sends, Email Sends, Email Sends and 26 more.
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.