朋友圈
来自 RSS 源的朋友最新动态
Connectivity Issues
Jun 24, 13:34 UTCResolved - Cloudflare have confirmed this issue is now resolved and all cdnjs services should be accessible again.Jun 24, 12:51 UTCMonitoring - Cloudflare and the responsible network for the route leak have now fixed the issue. Connectivity should now be recovering. We will continue to monitor the effects on the cdnjs services and follow updates from Cloudflare.Jun 24, 12:37 UTCUpdate - Cloudflare are still working to resolve the route leak that is causing major outages across the internet. Follow their status updates at https://www.cloudflarestatus.com/incidents/46z55mdhg0t5Jun 24, 11:57 UTCUpdate - Cloudflare have identified the network issue as a route leak and have their network operations team engaged in restoring services. Keep updated via their incident at https://www.cloudflarestatus.com/incidents/46z55mdhg0t5Jun 24, 11:28 UTCIdentified - We have been made aware of some users who are having connectivity issues to both our main website and the CDN service. We believe at this time that this is due to network issues that Cloudflare are experiencing. This is likely to also impact our API, though we have no reports of this yet. You can track the Cloudflare incident at https://www.cloudflarestatus.com/incidents/46z55mdhg0t5
Missing CORS Headers
Apr 15, 22:36 UTCResolved - Cloudflare have purged all affected resources from the cache and are confident that this issue has now been resolved.Apr 15, 20:20 UTCMonitoring - Cloudflare have released a fix for the issue. Please let us know via Twitter or our main GitHub repository if you continue to see issues.Twitter: https://twitter.com/cdnjs or https://twitter.com/cdnjsStatusGitHub: https://github.com/cdnjs/cdnjs/issues/13324Apr 15, 20:13 UTCIdentified - Cloudflare have identified the source of the issue and are currently working to roll out a fix to the missing CORS headers.Apr 15, 19:54 UTCInvestigating - We have been made aware of some responses lacking CORS headers from the CDN service. We are working with Cloudflare, who have recently deployed changes, to resolve this.
Resources not loading - 404/CORS
Feb 2, 10:00 UTCResolved - 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!Feb 1, 23:00 UTCMonitoring - 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.Feb 1, 21:15 UTCIdentified - 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.Feb 1, 18:30 UTCMonitoring - 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.Feb 1, 12:00 UTCUpdate - 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/13165Feb 1, 10:30 UTCInvestigating - 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.
Resources not loading - 404/CORS
Dec 28, 20:30 UTCResolved - We and Cloudflare are happy to say that the CDN is now performing normally.Dec 28, 12:00 UTCUpdate - 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.Dec 27, 12:15 UTCMonitoring - 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.Dec 26, 12:45 UTCUpdate - 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/13165Dec 25, 23:30 UTCUpdate - 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.Dec 23, 18:30 UTCUpdate - 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/13165Dec 23, 11:00 UTCIdentified - 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.Dec 22, 21:15 UTCUpdate - 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/13165Dec 22, 21:00 UTCInvestigating - 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.