CompaniesLaunchDarklyIncidents
LaunchDarkly: unpkg CDN caching broken JavaScript SDK release
Timeline of updates
- resolved
Earlier today we released JavaScript SDK 2.19.3. When we realized the release was broken, we deprecated the release and took it down. For a few hours, the unpkg CDN was caching an invalid URL. After rolling forward with a 2.19.4 release, the unpkg CDN is now returning a valid JS SDK release. Note that we do not recommend depending on open-source CDNs for serving the LaunchDarkly SDK in production environments.
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 2021-10-13 04:10 UTC, resolved after 0 min, 1 update(s).
- Title
- unpkg CDN caching broken JavaScript SDK release
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/mn953kxhsf1f
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on October 13, 2021LaunchDarkly in October 2021MarkdownJSON