CompaniesLaunchDarklyIncidents
LaunchDarkly: Elevated TLS negotiation error rate for server side SDKs in streaming mode
Timeline of updates
- resolved
Between 10:12 AM and 10:52 AM PT, a small subset of customers using LaunchDarkly server-side SDKs in streaming mode on older TLS versions may have experienced TLS negotiation errors when initializing SDKs. The issue has been fully resolved, and all services are now operating normally.
From LaunchDarkly’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.launchdarkly.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by LaunchDarkly, started 2025-08-28 17:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Elevated TLS negotiation error rate for server side SDKs in streaming mode
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/fq92n15zjsfq
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on August 28, 2025LaunchDarkly in August 2025MarkdownJSON