Iterable: Journey processing issues across clusters
Timeline of updates
- resolved
The engineering team has confirmed that journey processing is healthy and our systems have caught up on their processing backlogs. For the most part, impact was between approximately 3:00am PT and 9:20am PT today. Clusters 6 and 9 took a little longer to recover, so impact for those was between approximately 3:00am PT and 12:00pm PT.
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-08-27 16:10 UTC, resolved after 4.0 h, 1 update(s).
- Title
- Journey processing issues across clusters
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/x5yc1y4b5mv7
Iterable profileRecent Iterable incidentsAll outages on August 27, 2023Iterable in August 2023MarkdownJSON