Iterable: Degraded back-end processing
Timeline of updates
- resolved
We've identified and fixed the issue, data is processing as usual again. We apologize for any inconvenience.
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 2017-10-26 20:33 UTC, resolved after 30 min, 1 update(s).
- Title
- Degraded back-end processing
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/q33fj71zld5k
Iterable profileRecent Iterable incidentsAll outages on October 26, 2017Iterable in October 2017MarkdownJSON