LaunchDarkly incident: Frequentist experiments cannot be saved or started

Affected components

• Experiment management

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.

• ClickHouse Cloud: Cloud console UI downCritical · Jul 8, 2026, 19:30 UTC
• Supabase: Project status change failures in multiple regionsMajor · Jun 30, 2026, 02:38 UTC
• Mux: Live Stream DisruptionsMajor · Jul 8, 2026, 17:29 UTC
• Airtable: Airtable service unavailabilityMajor · Jul 8, 2026, 19:17 UTC
• Shippo: Australia Post – Delayed Tracking Event UpdatesMinor · Jul 6, 2026, 16:51 UTC
• Twilio: User Authentication Identity SNA Missing Redirects for Three in United KingdomMinor · Jul 7, 2026, 21:09 UTC
• Supabase: Project creation delays in AP regionsMinor · Jul 8, 2026, 16:52 UTC
• Calendly: Degraded performance on Calendly.comMinor · Jul 8, 2026, 17:25 UTC
• Anthropic: Elevated errors on multiple modelsMinor · Jul 8, 2026, 18:00 UTC
• Supabase: Elevated JWT authorization errorsMinor · Jul 8, 2026, 18:37 UTC

How often does LaunchDarkly have incidents?

LaunchDarkly reported 8 incidents in the last 90 days. A typical incident lasted 1h 26m. See LaunchDarkly's uptime and incident history