Minor impactResolvedDevOps

LaunchDarkly incident: Elevated Streaming Errors in Europe

LaunchDarkly reported this minor-impact incident on its official status page on May 4, 2026, 10:14 UTC. It was resolved after 6h 8m.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
May 4, 2026, 10:14 UTC
started
May 4, 2026, 16:23 UTC
resolved
6h 8m
duration
Minor
impact

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.

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