朋友圈
来自 RSS 源的朋友最新动态
API outage
Jun 12, 21:42 UTCResolved - Cloudflare has now marked its incident as resolved, and we are confident that the cdnjs API is now operating as normal.Jun 12, 20:31 UTCMonitoring - At this time, we're seeing cdnjs' API service recover and return to normal operation. We'll continue to monitor the service until the upstream provider indicates resolution and we're happy the service is stable.Jun 12, 19:18 UTCUpdate - Cloudflare has indicated that it is beginning to see recovery of its services. We continue to monitor the impact to cdnjs' API and will provide an update when it has recovered.Jun 12, 18:34 UTCIdentified - cdnjs' API is impacted by an ongoing outage with Cloudflare services: https://www.cloudflarestatus.com/incidents/25r9t0vz99rpJun 12, 18:20 UTCInvestigating - We're investigating an outage with the cdnjs API. We believe this to be caused by an upstream provider issue.
SRI hashes changed on multiple libraries
Aug 4, 15:33 UTCResolved - At this time we believe the fix to restore file content and SRI hashes is working as expected.Aug 2, 18:26 UTCMonitoring - A backfill has been completed that is believed to have restored files to their previous states, with the SRI hashes reverted to what they were prior to this incident. We'll continue to monitor for reports of any hash mismatches, which should be reported in the issue on GitHub at https://github.com/cdnjs/cdnjs/issues/14210Aug 1, 18:22 UTCIdentified - We are aware of an issue impacting multiple libraries where SRI hashes have changed. We have found the cause of the change to the file contents/hashes and are actively working to restore the previous contents/hashes. No files on the CDN have been compromised, the contents/hashes have changed due to libraries being reprocessed with different minification logic. We are tracking this on GitHub in https://github.com/cdnjs/cdnjs/issues/14210
API returning 502 responses
May 20, 21:45 UTCResolved - This incident has been resolved.May 20, 20:31 UTCMonitoring - At this time the API is now returning valid responses for all requests. We will continue to monitor the situation to ensure this remains true.May 20, 11:45 UTCUpdate - We are continuing to investigate the 502 issue with the API. It appears to be impacting a limited subset of requests at this time.May 20, 02:00 UTCInvestigating - We are aware that the cdnjs API is returning 502 responses for many requests. We are investigating this issue.(Edit: This incident has been back-dated to the believed initial starting point of impact for requests. Incident was initially declared at 11:30 UTC.)
Intermittent issues with API responses
May 25, 09:50 UTCResolved - The API service has now been restored.May 25, 09:40 UTCMonitoring - We are confident that a fix is now in place for the intermittent issues previously experienced by some users with the API service. We will continue to monitor the situation to ensure this remains the case.May 25, 09:01 UTCUpdate - Our team are online and have temporarily restored the API service. We continue to investigate the root cause and look for a solution.May 25, 08:56 UTCInvestigating - We are aware that some requests to the API may receive invalid responses. We are looking into this.
API returning Error 502 Bad Gateway
May 24, 22:59 UTCResolved - We are confident that the API service and the website are both stable.May 24, 22:40 UTCMonitoring - A further fix has been implemented and the API service appears to be healthy now. We will continue to monitor this.May 24, 22:02 UTCIdentified - 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.May 24, 21:53 UTCMonitoring - 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.May 24, 21:20 UTCUpdate - 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.May 24, 19:45 UTCInvestigating - 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.
Auto-update bot maintenance
May 10, 16:35 UTCCompleted - The scheduled maintenance has been completed.May 6, 16:36 UTCIn progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.May 6, 16:30 UTCScheduled - Maintenance work continues on the auto-update bot for cdnjs continues and as such it will be offline whilst this work is done. During this maintenance the addition of new libraries and new versions to the CDN will be delayed until the bot is re-enabled. Access to any existing library assets on CDN will not be affected.
Auto-update bot maintenance
May 6, 15:45 UTCCompleted - The scheduled maintenance has been completed.Apr 28, 15:45 UTCIn progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr 28, 15:36 UTCScheduled - Maintenance work on the auto-update bot for cdnjs continues and as such it will be offline whilst this work is done. During this maintenance the addition of new libraries and new versions to the CDN will be delayed until the bot is re-enabled. Access to any existing library assets on CDN will not be affected.
Auot-update maintenance
Apr 28, 15:30 UTCCompleted - The scheduled maintenance has been completed.Apr 26, 15:30 UTCIn progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr 26, 15:28 UTCScheduled - The auto-update bot for cdnjs has been taken offline while maintenance is being carried out. This does not affect existing libraries and versions on the CDN, they will remain available. During this time period the addition of new libraries and new versions to the CDN will be delayed until the bot is re-enabled.