API returning Error 502 Bad Gateway
Incident Report for cdnjs
Resolved
We are confident that the API service and the website are both stable.
Posted May 24, 2021 - 22:59 UTC
Monitoring
A further fix has been implemented and the API service appears to be healthy now. We will continue to monitor this.
Posted May 24, 2021 - 22:40 UTC
Identified
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.
Posted May 24, 2021 - 22:02 UTC
Monitoring
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.
Posted May 24, 2021 - 21:53 UTC
Update
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.
Posted May 24, 2021 - 21:20 UTC
Investigating
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.
Posted May 24, 2021 - 19:45 UTC
This incident affected: API (api.cdnjs.com) and Website (cdnjs.com).