Iterable: Data ingestion lag for a subset of customers
Timeline of updates
- resolved
Data ingestion delay has fully recovered and there are no further delays. Thank you for your patience as we worked through this issue today. If you have any questions or 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 2020-04-14 22:17 UTC, resolved after 2.0 h, 1 update(s).
- Title
- Data ingestion lag for a subset of customers
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/wk4nyyv2jr5g
Iterable profileRecent Iterable incidentsAll outages on April 14, 2020Iterable in April 2020MarkdownJSON