CompaniesLaunchDarklyIncidents
LaunchDarkly: Brief interruption of Mobile and Browser Streams
Timeline of updates
- resolved
At 13:00 PDT, a change to our platform caused a 17 minute interruption of updates for customers utilizing the mobile and browser SDKs. This change has been reverted and all systems are functioning normally as of 13:17 PDT. The expected impact is that between 13:00PDT and 13:17PDT, new connections from mobile and browser based SDKs would have failed to connect to our systems, and mutations to flag rules made during that period would not have been propagated to the clients. Affected clients would have continued serving the flag states they had prior to 13:00PDT The expected behavior of affected clients should be that they will retry to connect to the streams and will recover gracefully. Once reconnected, any mutations to flag rules will propagate. This will be the final communication about this incident.
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: none) posted by LaunchDarkly, started 2017-09-28 20:53 UTC, resolved after 0 min, 1 update(s).
- Title
- Brief interruption of Mobile and Browser Streams
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/jvdzr92fxmc0
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on September 28, 2017LaunchDarkly in September 2017MarkdownJSON