Iterable: Data ingestion lag for one server cluster
Timeline of updates
- resolved
Data ingestion is now fully-caught up at this point. Thank you for your patience. If you have any concerns please contact us 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 2019-07-17 16:39 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Data ingestion lag for one server cluster
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/8b9hv8qwglt0
Iterable profileRecent Iterable incidentsAll outages on July 17, 2019Iterable in July 2019MarkdownJSON