LaunchDarkly incident: Event processing delays

Affected components

• Experiment results processing
• Warehouse native experimentation

1. resolvedMar 11, 2026, 04:07 UTC

   The issue with Event processing has been resolved. Impacted services have returned to normal operation. Flag Delivery was not impacted. There was no data loss experienced.

2. monitoringMar 10, 2026, 23:42 UTC

   We are continuing to monitor for any further issues.

3. monitoringMar 10, 2026, 23:38 UTC

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

4. investigatingMar 10, 2026, 22:59 UTC

   Event processing is currently delayed for and will show stale data for several product areas, including: - Autogenerated metric creation - Data Export - Experimentation No data has been lost.

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.

• Snowflake: AWS - Middle East (UAE): INC0152681Critical · Mar 1, 2026, 13:33 UTC
• Grafana Cloud: Complete outage in prod-me-central-1Critical · Mar 2, 2026, 06:43 UTC
• Smartsheet: Brandfolder Monthly Reports DelayedMajor · Feb 27, 2026, 21:55 UTC
• MongoDB Atlas: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)Major · Mar 1, 2026, 19:30 UTC
• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Mar 2, 2026, 07:19 UTC
• MongoDB Atlas: Atlas Clusters Snapshot FailuresMajor · Mar 10, 2026, 23:18 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