LaunchDarkly incident: Elevated errors on server-side SDK streaming connections

Affected components

• SDKs

1. resolvedAug 7, 2026, 20:15 UTC

   SDKs restored to operational

2. investigatingAug 7, 2026, 20:12 UTC

   We are continuing to investigate this issue.

3. investigatingAug 7, 2026, 19:56 UTC

   We released several mitigations and we're noticing that error rates are dropping. We'll continue to monitor the situation.

4. investigatingAug 7, 2026, 19:29 UTC

   We are investigating elevated HTTP 500 errors affecting some server-side SDK streaming connections in our US commercial environment. Affected applications may fail to establish or may intermittently lose their streaming connection to LaunchDarkly.

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.

• Elasticsearch: Elasticsearch 9.5.0 contains a query-correctness defectMajor · Aug 5, 2026, 22:59 UTC
• Twilio: SMS Delivery Receipt Delays from Twilio to Liberty Mobile Puerto RicoMinor · Jul 29, 2026, 19:53 UTC
• Twilio: Voice Call Audio Quality Degradation From Network Subscribers to Twilio Colombia Landline NumbersMinor · Aug 6, 2026, 20:09 UTC
• Hugging Face: Elevated error rate - AWS CDN (Singapore)Minor · Aug 7, 2026, 15:14 UTC
• Twilio: Voice Call Failures from Twilio Phone Numbers to ChileMinor · Aug 7, 2026, 16:17 UTC
• Twilio: SMS Delivery Failures from a Subset of Twilio Alphanumeric Senders and Long Codes to Orange GuineaMinor · Aug 7, 2026, 17:02 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