cdnjs experienced a notice incident on February 1, 2019 affecting CDN Service (cdnjs.cloudflare.com), lasting 23h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 06, 2019, 04:02 PM UTC
It appears that the CDN is failing to serve a small minority of requests again. We have alerted Cloudflare and are waiting for their response.
- investigating Feb 06, 2019, 04:08 PM UTC
To assist in the diagnosis of the issue, please post any failed requests with full request/response headers on our GitHub mega-issue: https://github.com/cdnjs/cdnjs/issues/13165
- monitoring Feb 06, 2019, 04:11 PM UTC
Cloudflare have identified the issue a recurrence of the CDN failure we experienced in December. They have now fixed the issue and we are monitoring the CDN to ensure service is restored.
- identified Feb 06, 2019, 04:13 PM UTC
Further reports have been made of continued issues with the CDN and these have been passed on to Cloudflare to ensure that the issue is resolved in a timely manner. We apologise for the drop in service to those affected.
- monitoring Feb 06, 2019, 04:15 PM UTC
This issue had resurfaced due to an automatic process with Cloudflare reinstating a broken node into the load balancer. This has now been stopped and we will continue to monitor to ensure the CDN is performing normally.
- resolved Feb 06, 2019, 04:17 PM UTC
We believe that the CDN is now back to normal and service should be fully restored to cdnjs! Apologies from all of us here at cdnjs for the delay in getting this resolved and for the drop in service. Have a great weekend making use of cdnjs in all your projects!