CompaniesLaunchDarklyIncidents
LaunchDarkly: Elevated Client Stream API Errors
Timeline of updates
- resolved
We had experienced elevated client stream connection errors between 14:39 UTC - 15:56 UTC. Client-side SDK connecting around this time could see errors in logs and fallback to cached or default flag values. The issue is now resolved.
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 2022-06-17 15:03 UTC, resolved after 6.6 h, 1 update(s).
- Title
- Elevated Client Stream API Errors
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/4g0v7pnq0hmw
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on June 17, 2022LaunchDarkly in June 2022MarkdownJSON