LaunchDarkly incident: Experiment and multi-armed bandit results delayed

Affected components

• Experiment results processing

1. resolvedMay 4, 2026, 20:25 UTC

   All experiment and multi-armed bandit result data is caught up. No data was lost.

2. monitoringMay 4, 2026, 20:19 UTC

   We have implemented a fix and are catching up on backlogged data. We estimate that we will be fully caught up in about 1 hour.

3. identifiedMay 4, 2026, 19:50 UTC

   We have identified the issue and are continuing our work to resolve it.

4. investigatingMay 4, 2026, 19:47 UTC

   We are currently investigating delays in experiment and multi-armed bandit results. Data is currently delayed by 1-2 hours. No data loss is expected.

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.

• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: (Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]Minor · May 1, 2026, 17:51 UTC
• Twilio: Voice Call Audio Quality Degradation Between Twilio Phone Numbers and Multiple Networks in United KingdomMinor · May 2, 2026, 18:00 UTC
• Twilio: SMS Delivery Delays From Multiple Networks in Croatia to Twilio Long CodesMinor · May 4, 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