CompaniesLaunchDarklyIncidents
LaunchDarkly: Issue saving targeting rules with semantic versioning operators
Timeline of updates
- resolved
This issue turned out to be a false alarm; flag targeting rules are being saved correctly.
From LaunchDarkly’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.launchdarkly.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by LaunchDarkly, started 2022-07-26 15:42 UTC, resolved after 30 min, 1 update(s).
- Title
- Issue saving targeting rules with semantic versioning operators
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/sftknmp6kn37
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on July 26, 2022LaunchDarkly in July 2022MarkdownJSON