cdnjs experienced a notice incident on December 22, 2018 affecting CDN Service (cdnjs.cloudflare.com), lasting 5d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 06, 2019, 03:34 PM UTC
We have been made aware that our CDN is in a small number of requests giving an invalid response that is a 404 with missing CORS headers. We are currently investigating this and will post an update here shortly.
- investigating Feb 06, 2019, 03:37 PM UTC
To help us with investigating this issue we have created a GitHub mega-issue. Please post any failed requests will full request/response headers and the resource URL that failed: https://github.com/cdnjs/cdnjs/issues/13165
- identified Feb 06, 2019, 03:39 PM UTC
We believe we have identified the issue relating to the minority of requests that are receiving a bad response. We have alerted Cloudflare to this and are currently awaiting their response to resolve this.
- identified Feb 06, 2019, 03:42 PM UTC
We are aware that a higher percentage of requests are beginning to fail now. We apologise for the delay in resolving this. Please continue to post full request/response headers on the GitHub mega-issue to assist Cloudflare in resolving this: https://github.com/cdnjs/cdnjs/issues/13165
- identified Feb 06, 2019, 03:45 PM UTC
Cloudflare are now handling this issue and actively looking to resolve it as it is a failure of their infrastructure behind cdnjs that is causing this issue. They apologise for any delay due to engineering staff being away on holiday leave.
- identified Feb 06, 2019, 03:48 PM UTC
To assist Cloudflare in identifying bad origin servers for the CDN, please post any failed requests on our GitHub mega-issue with full request and response headers along with the resource URL that failed: https://github.com/cdnjs/cdnjs/issues/13165
- monitoring Feb 06, 2019, 03:50 PM UTC
Cloudflare have now identified the failing origin servers and they have been removed from the load balancer. CDN responses should now return to normal and cdnjs/Cloudflare will continue to monitor this.
- monitoring Feb 06, 2019, 03:52 PM UTC
We believe that the CDN is now serving all requests with valid responses. We sincerely apologise for the long delay in resolving this issue. We will continue to monitor the situation for a while longer to confirm all is okay.
- resolved Feb 06, 2019, 03:53 PM UTC
We and Cloudflare are happy to say that the CDN is now performing normally.