CompaniesLaunchDarklyIncidents
LaunchDarkly: Fastly incident
Timeline of updates
- resolved
The incident has been resolved. For more details on the underlying cause, see Fastly's status page: https://status.fastly.com/incidents/pfw3gml89bz2 (opens in new tab)
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 2016-10-25 19:22 UTC, resolved after 2.6 h, 1 update(s).
- Title
- Fastly incident
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/2kmrzm722x3j
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on October 25, 2016LaunchDarkly in October 2016MarkdownJSON