cdnjs incident

Library versions missing from website & API

Minor Resolved View vendor source →

cdnjs experienced a minor incident on December 30, 2019 affecting API (api.cdnjs.com) and Website (cdnjs.com), lasting 7h 20m. The incident has been resolved; the full update timeline is below.

Started
Dec 30, 2019, 09:59 AM UTC
Resolved
Dec 30, 2019, 05:19 PM UTC
Duration
7h 20m
Detected by Pingoru
Dec 30, 2019, 09:59 AM UTC

Affected components

API (api.cdnjs.com)Website (cdnjs.com)

Update timeline

  1. investigating Dec 30, 2019, 09:59 AM UTC

    We have been made aware of an issue with the cdnjs website that means certain library pages are not showing, with an error message "version not found!" shown instead. Further, it appears that on the same libraries, their API responses do not contain the correct versions. This does not affect the libraries available on the CDN, cdnjs.cloudflare.com.

  2. identified Dec 30, 2019, 03:33 PM UTC

    We have identified the issue as a fault within our package generation script that feeds cdnjs repository information to our website & API. We are tracking this issue on GitHub: https://github.com/cdnjs/cdnjs/issues/13654

  3. monitoring Dec 30, 2019, 03:35 PM UTC

    We have now implemented a fix and believe that packages should now be showing correctly on the cdnjs website and via the API. We will continue to monitor this whilst the caches clear to ensure this issue is no longer present.

  4. resolved Dec 30, 2019, 05:19 PM UTC

    We are now confident the fix is working as expected. The cdnjs website and API are now showing libraries and their versions correctly.