cdnjs incident

cdnjs website & API erroring for some libraries

Minor Resolved View vendor source →

cdnjs experienced a minor incident on June 12, 2020 affecting API (api.cdnjs.com) and Website (cdnjs.com), lasting 3h 47m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2020, 08:30 AM UTC
Resolved
Jun 12, 2020, 12:18 PM UTC
Duration
3h 47m
Detected by Pingoru
Jun 12, 2020, 08:30 AM UTC

Affected components

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

Update timeline

  1. investigating Jun 12, 2020, 08:30 AM UTC

    We are aware of reports that some libraries on the cdnjs website and API are resulting in an error response. We have notified our team and are looking into the root cause of this issue.

  2. identified Jun 12, 2020, 09:25 AM UTC

    We have identified the source of the failure, the metadata used for the website and API for packages data was unable to generate correctly, resulting in the data used being corrupted. We are working to mitigate this and regenerate the data.

  3. identified Jun 12, 2020, 10:30 AM UTC

    The cdnjs API is now correctly responding to library requests, however, we are still working to resolve the issue present on the website.

  4. monitoring Jun 12, 2020, 11:15 AM UTC

    The cdnjs website and API are now both using updated packages metadata, allowing them to correctly respond to requests for libraries without error. We will continue to monitor both the API and website to ensure this doesn't happen again.

  5. resolved Jun 12, 2020, 12:18 PM UTC

    We are confident at this time that we have resolved the errors seen with the website & API, both are now handling library requests correctly.