LaunchDarkly incident: Elevated Streaming Errors in Europe

Affected components

• Server-side streaming API

1. resolvedMay 4, 2026, 16:23 UTC

   This incident has been resolved.

2. monitoringMay 4, 2026, 15:47 UTC

   We've implemented a fix and have mitigated impact as of 8:35am PT. Streaming SDKs should be able to connect successfully at this time.

3. identifiedMay 4, 2026, 14:30 UTC

   We're continuing to address the root cause of the elevated error rate. Server SDKs may require additional time to initialize while requests are retried.

4. identifiedMay 4, 2026, 12:51 UTC

   We're identified an infrastructure issue causing elevated error rates and are working on a fix.

5. investigatingMay 4, 2026, 10:14 UTC

   We are investigating elevated error rates for streaming initialization in the Europe region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting 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.

• GitBook: 500 errors on some *.gitbook.io published sitesMajor · May 4, 2026, 11:55 UTC
• Contentful: Some customers are experiencing issues logging inMajor · May 4, 2026, 13:20 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 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