CompaniesLaunchDarklyIncidents
LaunchDarkly: Errors on streaming SDK initialization
Timeline of updates
- resolved
We've identified an infrastructure issue that caused some 503 responses in feature flagging streaming client initialization on the US LaunchDarkly instance between 16:45 and 17:05 PT. SDKs should automatically retry initialization in most cases.
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
76243b9ab27a62f9…
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: none) posted by LaunchDarkly, started 2026-04-30 00:30 UTC, resolved after -45 min, 1 update(s).
- Title
- Errors on streaming SDK initialization
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/4th4z5b2thm4
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on April 30, 2026LaunchDarkly in April 2026MarkdownJSON