Minor impactResolvedDevOps

LaunchDarkly incident: Elevated Streaming Errors in APAC region

LaunchDarkly reported this minor-impact incident on its official status page on May 6, 2026, 03:58 UTC. It was resolved after 28 min.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
May 6, 2026, 03:58 UTC
started
May 6, 2026, 04:26 UTC
resolved
28 min
duration
Minor
impact

Affected components

  • Server-side streaming API
  1. resolvedMay 6, 2026, 04:26 UTC

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

  2. identifiedMay 6, 2026, 04:00 UTC

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

  3. investigatingMay 6, 2026, 03:58 UTC

    We are investigating elevated error rates for streaming initialization in the APAC 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 9 incidents in the last 90 days. A typical incident lasted 1h 15m. See LaunchDarkly's uptime and incident history