Minor impactResolvedDevOps

LaunchDarkly incident: Issue with Experiment Results in case of Flag Variation edits

LaunchDarkly reported this minor-impact incident on its official status page on Apr 29, 2026, 20:19 UTC. It was resolved after 1d 3h.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
Apr 29, 2026, 20:19 UTC
started
May 1, 2026, 00:09 UTC
resolved
1d 3h
duration
Minor
impact

Affected components

  • Experiment results analysis
  • Experiment results processing
  1. resolvedMay 1, 2026, 00:09 UTC

    We have validated a fix to resolve all remaining experiments with inaccurate sample ratio mismatches (SRMs) or empty experiment results. The vast majority of experiments and experimentation customers were not impacted.

  2. monitoringApr 30, 2026, 00:04 UTC

    We've released a fix to prevent this issue in new experiments and iterations. We're working to resolve this issue for experiment data recently processed.

  3. identifiedApr 29, 2026, 20:49 UTC

    We've identified the issue and are implementing a fix for this behavior.

  4. investigatingApr 29, 2026, 20:19 UTC

    We are aware of an issue affecting some customers that may result in sample ratio mismatches (SRMs) or empty experiment results if flag variations are edited between experiment iterations.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in LaunchDarkly's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does LaunchDarkly have incidents?

LaunchDarkly reported 15 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 19m. See LaunchDarkly's uptime and incident history

LaunchDarkly incident on Apr 29, 2026: Issue with Experiment Results in case of Flag Variation edits · APIStatus.watch