LaunchDarkly incident

Elevated Streaming Errors in APAC region

Minor Resolved View vendor source →

LaunchDarkly experienced a minor incident on May 6, 2026 affecting Server-side streaming API, lasting 27m. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 03:58 AM UTC
Resolved
May 06, 2026, 04:26 AM UTC
Duration
27m
Detected by Pingoru
May 06, 2026, 03:58 AM UTC

Affected components

Server-side streaming API

Update timeline

  1. investigating May 06, 2026, 03:58 AM UTC

    We are investigating elevated error rates for streaming initialization in the APAC region. Some customers using streaming server-side SDKs in the APAC region with may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.

  2. identified May 06, 2026, 04:00 AM UTC

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

  3. resolved May 06, 2026, 04:26 AM 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.

Looking to track LaunchDarkly downtime and outages?

Pingoru polls LaunchDarkly's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when LaunchDarkly reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track LaunchDarkly alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring LaunchDarkly for free

5 free monitors · No credit card required