LaunchDarkly incident: delayed event processing

Affected components

• Experiment results processing
• Flag usage metrics
• Metrics
• OpenTelemetry (Logs, Traces, Metrics)
• Rollout results processing

1. resolvedOct 26, 2026, 20:52 UTC

   A scaling inflection point in our realtime event warehouse led to a delay for some event ingestion. The engineering team has remediated the problem and all events should be caught up. Some customers may have seen delays in experiments and in guarded release processing. This is now resolved and the team will carefully monitor.

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.

• Twilio: SMS Delivery Delays from Twilio to Claro Costa RicaMinor · Oct 24, 2026, 00:48 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Phone Numbers to C-Spire United StatesMinor · Oct 24, 2026, 19:28 UTC
• Akamai: Edge Delivery issues between Indonesia and SingaporeMinor · Oct 25, 2026, 13:44 UTC
• Linode: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)Minor · Oct 25, 2026, 13:54 UTC
• Twilio: Voice Call Failures from Twilio Phone Numbers to RomaniaMinor · Oct 26, 2026, 13:09 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio to Mauritel MauritaniaMinor · Oct 26, 2026, 14:20 UTC
• Netlify: Delays in build logs appearing in the UIMinor · Oct 26, 2026, 16:05 UTC
• Twilio: MMS Delivery Delays and Failures from a Subset of Twilio Long Codes to Cellcom United StatesMinor · Oct 26, 2026, 20:29 UTC

How often does LaunchDarkly have incidents?

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