CompaniesLaunchDarklyIncidents
LaunchDarkly: Elevated errors on server-side SDK streaming connections
Affected components: SDKs
Timeline of updates
- investigating
We are investigating elevated HTTP 500 errors affecting some server-side SDK
streaming connections in our US commercial environment. Affected applications
may fail to establish or may intermittently lose their streaming connection to
LaunchDarkly. - investigating
We released several mitigations and we're noticing that error rates are dropping. We'll continue to monitor the situation.
- investigating
We are continuing to investigate this issue.
- resolved
SDKs restored to operational
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
92abfb4908a7a70e…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by LaunchDarkly, started 2026-08-07 19:29 UTC, resolved after 46 min, 4 update(s).
- Title
- Elevated errors on server-side SDK streaming connections
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/jfz9d916tq56
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on August 7, 2026LaunchDarkly in August 2026MarkdownJSON