CompaniesLaunchDarklyIncidents
LaunchDarkly: Unprocessed A/B Testing Data
Timeline of updates
- resolved
This incident has been resolved. Testing data sent between June 18th 2:30pm PDT and June 19th 2:30pm PDT have been recovered. However, conversion data sent between June 17th 2:30pm PDT and June 18th 2:30pm PDT has been lost. The result being that any tests active during this time will take longer to complete, likely one additional day. We apologies for any inconveniences this may have caused and should you have further concerns please contact us at support@launchdarkly.com.
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 2019-06-19 21:43 UTC, resolved after 25 h, 1 update(s).
- Title
- Unprocessed A/B Testing Data
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/qpd849h0dfmk
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on June 19, 2019LaunchDarkly in June 2019MarkdownJSON