Iterable: Data ingestion slow for some customers
Timeline of updates
- resolved
Data ingestion continues to behave as expected, so we're going to move this to resolved status. Thank you for your patience if you were affected by the delays this morning.
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 2019-02-01 17:07 UTC, resolved after 4.9 h, 1 update(s).
- Title
- Data ingestion slow for some customers
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/c0kfwc1fccln
Iterable profileRecent Iterable incidentsAll outages on February 1, 2019Iterable in February 2019MarkdownJSON