LaunchDarkly incident: Delay in Experimentation Results and Experimentation Warehouse Data Export

Affected components

• Experiment results processing
• Warehouse native experimentation

1. resolvedMay 2, 2026, 19:15 UTC

   Experimentation results processing and data warehouse export was caught up as of 12:28 pm PT.

2. monitoringMay 2, 2026, 13:51 UTC

   We have implemented a fix and are catching up on backlogged experimentation results and data export. We estimate that we will be fully caught up in about 8 hours.

3. identifiedMay 2, 2026, 13:17 UTC

   We've identified the root cause of the experimentation results processing and data export delays and are working on implementing a fix.

4. investigatingMay 2, 2026, 12:55 UTC

   We are investigating an issue causing delayed experimentation results processing and delayed experimentation data warehouse export.

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.

• Discord: Message Sends affected on certain channelsMajor · May 2, 2026, 17:03 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Linode: Service Issue - Connectivity Issues - Chennai (IN-MAA)Minor · Apr 28, 2026, 17:17 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · Apr 29, 2026, 05:19 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

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