Minor impactResolvedDevOps

LaunchDarkly incident: Frequentist experiments cannot be saved or started

LaunchDarkly reported this minor-impact incident on its official status page on Jul 8, 2026, 18:03 UTC. It was resolved after 1h 38m.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
Jul 8, 2026, 18:03 UTC
started
Jul 8, 2026, 19:41 UTC
resolved
1h 38m
duration
Minor
impact

Affected components

  • Experiment management

Timeline

updates from LaunchDarkly's status page ↗
  1. resolvedJul 8, 2026, 19:41 UTC

    This incident has been resolved.

  2. monitoringJul 8, 2026, 18:51 UTC

    A fix has been implemented and we are monitoring the results.

  3. identifiedJul 8, 2026, 18:12 UTC

    We have identified the issue and are working towards releasing a fix.

  4. investigatingJul 8, 2026, 18:03 UTC

    We are currently investigating an issue where experiments using frequentist analysis cannot be saved or started.

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

← Previous: High volume of error alerts related to flag delivery network. (Jul 6, 2026)Next: LaunchDarkly is operational but customer action may be required (Jul 10, 2026) →
LaunchDarkly incident on Jul 8, 2026: Frequentist experiments cannot be saved or started · APIStatus.watch