Iterable: Degraded performance on C16
Timeline of updates
- resolved
Our engineering team has verified Cluster 16 has recovered. The issue is now resolved. Should you experience issues, please contact support at support@iterable.com.
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 2024-01-10 17:57 UTC, resolved after 26 h, 1 update(s).
- Title
- Degraded performance on C16
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/b02cgwpgn3y7
Iterable profileRecent Iterable incidentsAll outages on January 10, 2024Iterable in January 2024MarkdownJSON