Iterable: Slowness In Journeys Processing
Timeline of updates
- resolved
The original journey performance issues that triggered this incident have now been resolved. As mentioned in previous updates, there may be customers that have experienced users stuck in journey tiles as an effect of this incident. For these customers, our Customer Success team will be working with you separately to address these users on a case by case basis. Because the original impact is resolved, this incident will be closed, and a root cause analysis will be in progress. If you experience further journey performance issues, please reach out the Support team.
From Iterable’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.iterable.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Iterable, started 2023-06-27 15:53 UTC, resolved after 2 d, 1 update(s).
- Title
- Slowness In Journeys Processing
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/v8v7h603lsbq
Iterable profileRecent Iterable incidentsAll outages on June 27, 2023Iterable in June 2023MarkdownJSON