LaunchDarkly outage: Event Ingestion Delays

Affected components

• Experiment results processing
• Rollout results processing

1. resolvedMay 19, 2026, 14:54 UTC

   This incident has been resolved. Event ingestion is operating normally and all Experimentation results and Guarded Rollouts are fully restored. No data was lost. We apologize for any inconvenience caused. Results were delayed from 6:58am PDT to 7:52am PDT

2. identifiedMay 19, 2026, 14:49 UTC

   We are currently experiencing delays in event ingestion, which is impacting Experimentation results and Guarded Rollouts. No data has been lost — all results and events are intact and will be fully accessible once a fix has been deployed. We have identified the root cause and a fix is being released now.

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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• ClickHouse Cloud: GCP us-east1 capacity constraints impacting cluster operationsMinor · May 18, 2026, 12:31 UTC
• Snyk: Supply Chain Compromise on  @antv being investigated for more than 300 packages in npm ecosystemMinor · May 19, 2026, 05:29 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Snyk: Jira Integration DegradedMinor · May 19, 2026, 14:19 UTC
• Netlify: Degraded performance with Create APIMinor · May 19, 2026, 14:26 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