LaunchDarkly incident

Investigating - Increase in SDK errors

Minor Resolved View vendor source →

LaunchDarkly experienced a minor incident on December 15, 2025 affecting Server-side streaming API and Flag targeting and 1 more component, lasting 2h 24m. The incident has been resolved; the full update timeline is below.

Started
Dec 15, 2025, 02:14 PM UTC
Resolved
Dec 15, 2025, 04:38 PM UTC
Duration
2h 24m
Detected by Pingoru
Dec 15, 2025, 02:14 PM UTC

Affected components

Server-side streaming APIFlag targetingClient-side streaming APIPolling API

Update timeline

  1. investigating Dec 15, 2025, 02:14 PM UTC

    We are investigating an increase in SDK error rates affecting a small portion of requests, currently estimated at less than one percent. SDKs will automatically retry these errors, so the primary customer impact is expected to be longer SDK initialization times rather than request failures. We believe the issue is related to an ongoing incident affecting one of our vendors. Our team is actively working to mitigate the impact and will provide additional updates as more information becomes available.

  2. investigating Dec 15, 2025, 02:42 PM UTC

    We are continuing to investigate this issue.

  3. investigating Dec 15, 2025, 03:03 PM UTC

    We are also observing a small percentage timeouts when modifying feature flags via our API or UI. We are continuing to investigate this error.

  4. investigating Dec 15, 2025, 03:22 PM UTC

    We are continuing to investigate this issue.

  5. identified Dec 15, 2025, 03:31 PM UTC

    The issue has been identified and a fix is being implemented.

  6. identified Dec 15, 2025, 03:43 PM UTC

    We are observing a reduction in SDK errors. We are continuing to work on a fix.

  7. monitoring Dec 15, 2025, 04:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved Dec 15, 2025, 04:38 PM UTC

    This incident has been resolved.