CompaniesLaunchDarklyIncidents
LaunchDarkly: User Saving Failure
Timeline of updates
- resolved
A change made to the system that manages indexing user data for searching and displaying on the Users page resulted in a ramping failure in that system. The impact is that information regarding users who received flags or which attributes were being passed into the platform from ~8am October 8th to 1:49 pm PDT October 9th may not have been recorded. As such, some new users might not have been automatically recorded from this time, nor updates made on users. There was no impact on flag evaluation, targeting, audit logging, or any other mission critical platform capability. This is now resolved and there will be no further communications regarding this incident.
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 2017-10-09 20:50 UTC, resolved after 3.2 h, 1 update(s).
- Title
- User Saving Failure
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/j05zdqt6y0qt
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on October 9, 2017LaunchDarkly in October 2017MarkdownJSON