Amplitude: User property and propensity cohort filters did not work as expected
Timeline of updates
- resolved
Cohort definitions for user property and propensity filters did not honor the original user property/propensity definition users intended when they created the cohorts What Happened? The logic for the “did”/”did not” drop-down during the creation step was inverted, creating unexpected definitions and wrong results from Sept 23-Sept 26 Solution Deployed a UI fix so that the logic for “did”/”did not” is no longer inverted Did data correction for the definitions of affected cohorts on the database so we can honor the original intent the users when they first created these cohorts
From Amplitude’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.amplitude.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Amplitude, started 2022-09-23 20:30 UTC, resolved after 0 min, 1 update(s).
- Title
- User property and propensity cohort filters did not work as expected
- Vendor
- Amplitude
- Date
- URL
- https://rewindex.com/company/amplitude/incidents/5q28xnlmz2kd
Amplitude profileRecent Amplitude incidentsAll outages on September 23, 2022Amplitude in September 2022MarkdownJSON