Iterable: Stuck users across multiple journeys
Timeline of updates
- resolved
All remaining stuck users have been auto-removed from journeys yesterday Tuesday, November 14 and this incident is now resolved. If you need any further assistance related to this incident, please reach out to support for assistance.
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: none) posted by Iterable, started 2023-11-01 21:59 UTC, resolved after 14 d, 1 update(s).
- Title
- Stuck users across multiple journeys
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/fb3wcfmcx4yq
Iterable profileRecent Iterable incidentsAll outages on November 1, 2023Iterable in November 2023MarkdownJSON