Iterable: Overwrite of SignupDate field on user profiles and ingestion lag
Timeline of updates
- resolved
We've completed data validation for all affected customers and are satisfied that everything should be as expected. If you see any unusual sending behavior from 2/26-2/28 related to users in segmentations that use the signupDate, it could have been part of this incident. Please let us know if you have any questions: 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-03-01 00:35 UTC, resolved after 4 d, 1 update(s).
- Title
- Overwrite of SignupDate field on user profiles and ingestion lag
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/xn5lp2v6yzjc
Iterable profileRecent Iterable incidentsAll outages on March 1, 2019Iterable in March 2019MarkdownJSON