朋友圈
来自 RSS 源的朋友最新动态
API returning Argo Tunnel error
Apr 21, 17:45 UTCResolved - This incident has been resolved.Apr 21, 17:00 UTCMonitoring - The API is now responding nominally. We will continue to monitor the situation to ensure the cdnjs API remains stable.Apr 21, 16:30 UTCInvestigating - We are aware that the cdnjs API is currently returning an Argo Tunnel error. We are investigating this and will provide an update as soon as we know more.
Auto-update maintenance
Apr 7, 12:30 UTCCompleted - The scheduled maintenance has been completed.Apr 6, 20:30 UTCIn progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr 6, 19:00 UTCScheduled - The auto-update bot for cdnjs will be offline for a period of time as we work on some security maintenance. During this time no libraries will be updated on cdnjs, but once the maintenance has concluded we will be able to back-fill these automatically.
Auto-update bot maintenance
Nov 16, 12:55 UTCCompleted - At this time we are confident the auto-update bot has caught up with the backlog of new library versions and is stable following the changes made, concluding the maintenance.Nov 13, 16:55 UTCVerifying - The team has now re-enabled the auto-update bot and we are currently monitoring the bot to ensure the updates made are stable. The bot will now begin to push the backlog of new library versions published during the maintenance window to the CDN.Nov 12, 22:00 UTCIn progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. This work is expected to last for approximately 24 hours.Nov 12, 21:55 UTCScheduled - The auto-update bot for cdnjs is offline while maintenance is being carried out. This does not affect existing libraries and versions on the CDN, they will remain available. However, any new versions of libraries that are released during this time period will be delayed in being added to the CDN until the bot is re-enabled.
SSL errors for cdnjs.cloudflare.com
Aug 12, 15:26 UTCResolved - At this time we are confident that access to the CDN has been restored for all users of cdnjs.Aug 12, 14:56 UTCMonitoring - A fix has been implemented that should allow users in mainland China to access cdnjs. Cloudflare will continue to monitor the situation.Aug 12, 11:10 UTCIdentified - Cloudflare has now implemented a fix for the CDN and SSL errors should begin to resolve.Users in mainland China may still see issues connecting to cdnjs and we continue to work to resolve this.Aug 12, 10:31 UTCUpdate - The team at Cloudflare are aware of the issue and are working to fix it. You can track their updates at https://www.cloudflarestatus.com/incidents/vtlmfzqmc8h7 -- we will continue to share updates here as well.Aug 12, 10:25 UTCInvestigating - We are aware that requests to cdnjs.cloudflare.com are currently returning a bad SSL response. We are working to establish the root cause and get a fix implemented.
cdnjs website & API erroring for some libraries
Jun 12, 12:18 UTCResolved - We are confident at this time that we have resolved the errors seen with the website & API, both are now handling library requests correctly.Jun 12, 11:15 UTCMonitoring - The cdnjs website and API are now both using updated packages metadata, allowing them to correctly respond to requests for libraries without error. We will continue to monitor both the API and website to ensure this doesn't happen again.Jun 12, 10:30 UTCUpdate - The cdnjs API is now correctly responding to library requests, however, we are still working to resolve the issue present on the website.Jun 12, 09:25 UTCIdentified - We have identified the source of the failure, the metadata used for the website and API for packages data was unable to generate correctly, resulting in the data used being corrupted. We are working to mitigate this and regenerate the data.Jun 12, 08:30 UTCInvestigating - We are aware of reports that some libraries on the cdnjs website and API are resulting in an error response. We have notified our team and are looking into the root cause of this issue.
522 & 523 responses for non-cached assets
Apr 15, 21:50 UTCResolved - We are confident at this time that all cdnjs assets are now available on the CDN once again. Cloudflare is continuing to see good recovery on their incident as well: https://cfl.re/2VbxQ96Apr 15, 20:03 UTCMonitoring - It would appear the origins for cdnjs.cloudflare.com are now available again and requests to uncached cdnjs assets should now work as expected. We will continue to monitor for a while to ensure this is stable. For more information on the larger Cloudflare outage, please follow their status page updates: https://cfl.re/2VbxQ96Apr 15, 19:28 UTCIdentified - We believe this is due to the ongoing incident Cloudflare has: https://cfl.re/2VbxQ96 - Requests to cached assets should work but any request for an asset not cached on cdnjs is likely to fail at present.Apr 15, 19:01 UTCInvestigating - We are aware of an issue affecting requests for certain assets resulting in a 522 or 523 response. We are currently investigating the source of this issue.
Library versions missing from website & API
Dec 30, 17:19 UTCResolved - We are now confident the fix is working as expected. The cdnjs website and API are now showing libraries and their versions correctly.Dec 30, 15:35 UTCMonitoring - We have now implemented a fix and believe that packages should now be showing correctly on the cdnjs website and via the API. We will continue to monitor this whilst the caches clear to ensure this issue is no longer present.Dec 30, 15:33 UTCIdentified - We have identified the issue as a fault within our package generation script that feeds cdnjs repository information to our website & API. We are tracking this issue on GitHub: https://github.com/cdnjs/cdnjs/issues/13654Dec 30, 09:59 UTCInvestigating - We have been made aware of an issue with the cdnjs website that means certain library pages are not showing, with an error message "version not found!" shown instead. Further, it appears that on the same libraries, their API responses do not contain the correct versions. This does not affect the libraries available on the CDN, cdnjs.cloudflare.com.
502 Bad Gateway
Jul 2, 14:59 UTCResolved - Cloudflare is confident at this time that services have been restored to normal and users should no longer be affected by this outage. At this time we will, therefore, mark the incident as resolved. If you are still seeing any issues with the cdnjs services, please let us know through Twitter and we can look into it further.Jul 2, 14:17 UTCMonitoring - Cloudflare is stating that they have implemented a fix for this issue, we will continue to monitor our own user reports of any further outages and also monitor the Cloudflare incident.Jul 2, 14:02 UTCUpdate - Cloudflare have now raised an incident on their status page due to the outage: https://www.cloudflarestatus.com/incidents/tx4pgxs6zxdrJul 2, 13:53 UTCInvestigating - We are aware of reports from users that cdnjs (website & CDN) is returning 502 Bad Gateway errors. We believe this is a larger issue with Cloudflare itself as many other websites behind them are also down. We will keep this updated as we know more.