cdnjs experienced a critical incident on May 24, 2021 affecting API (api.cdnjs.com) and Website (cdnjs.com), lasting 3h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 24, 2021, 08:41 PM UTC
We are aware that the cdnjs API is currently returning a 502 Bad Gateway error for requests. We are investigating this and will update once we know more.
- investigating May 24, 2021, 09:20 PM UTC
We continue to investigate the 502 error issue with the API and are aware that this may also be impacting accessing library information on the cdnjs website as this is backed by the cdnjs API service.
- monitoring May 24, 2021, 09:53 PM UTC
We have implemented a fix for the 502 issues -- the API service, as well as the website, appears to be operational once again. We will continue to monitor the situation to ensure this remains the case.
- identified May 24, 2021, 10:02 PM UTC
We are aware of a secondary issue where some requests are receiving a 530/1016 Origin DNS error and we are working to resolve this.
- monitoring May 24, 2021, 10:40 PM UTC
A further fix has been implemented and the API service appears to be healthy now. We will continue to monitor this.
- resolved May 24, 2021, 10:59 PM UTC
We are confident that the API service and the website are both stable.