CompaniesLaunchDarklyIncidents
LaunchDarkly: Delayed historic results for running CUPED experiments
Timeline of updates
- resolved
The issue with delayed historic results for recently started CUPED experiments has been resolved. All data has been backfilled.
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: minor) posted by LaunchDarkly, started 2025-02-03 18:58 UTC, resolved after 5.7 h, 1 update(s).
- Title
- Delayed historic results for running CUPED experiments
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/4x43l3dm599z
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on February 3, 2025LaunchDarkly in February 2025MarkdownJSON