Jun <var data-var='date'>12</var>, <var data-var='time'>21:42</var> UTC Resolved - Cloudflare has now marked its incident as resolved, and we are confident that the cdnjs API is now operating as normal.Jun <var data-var='date'>12</var>, <var data-var='time'>20:31</var> UTC Monitoring - 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 <var data-var='date'>12</var>, <var data-var='time'>19:18</var> UTC Update - 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 <var data-var='date'>12</var>, <var data-var='time'>18:34</var> UTC Identified - cdnjs' API is impacted by an ongoing outage with Cloudflare services: https://www.cloudflarestatus.com/incidents/25r9t0vz99rpJun <var data-var='date'>12</var>, <var data-var='time'>18:20</var> UTC Investigating - We're investigating an outage with the cdnjs API. We believe this to be caused by an upstream provider issue.

API outage

Aug <var data-var='date'> 4</var>, <var data-var='time'>15:33</var> UTC Resolved - At this time we believe the fix to restore file content and SRI hashes is working as expected.Aug <var data-var='date'> 2</var>, <var data-var='time'>18:26</var> UTC Monitoring - 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 <var data-var='date'> 1</var>, <var data-var='time'>18:22</var> UTC Identified - 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

SRI hashes changed on multiple libraries

May <var data-var='date'>20</var>, <var data-var='time'>21:45</var> UTC Resolved - This incident has been resolved.May <var data-var='date'>20</var>, <var data-var='time'>20:31</var> UTC Monitoring - 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 <var data-var='date'>20</var>, <var data-var='time'>11:45</var> UTC Update - 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 <var data-var='date'>20</var>, <var data-var='time'>02:00</var> UTC Investigating - 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.)

API returning 502 responses

May <var data-var='date'>25</var>, <var data-var='time'>09:50</var> UTC Resolved - The API service has now been restored.May <var data-var='date'>25</var>, <var data-var='time'>09:40</var> UTC Monitoring - 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 <var data-var='date'>25</var>, <var data-var='time'>09:01</var> UTC Update - Our team are online and have temporarily restored the API service. We continue to investigate the root cause and look for a solution.May <var data-var='date'>25</var>, <var data-var='time'>08:56</var> UTC Investigating - We are aware that some requests to the API may receive invalid responses. We are looking into this.

Intermittent issues with API responses

May <var data-var='date'>24</var>, <var data-var='time'>22:59</var> UTC Resolved - We are confident that the API service and the website are both stable.May <var data-var='date'>24</var>, <var data-var='time'>22:40</var> UTC Monitoring - A further fix has been implemented and the API service appears to be healthy now. We will continue to monitor this.May <var data-var='date'>24</var>, <var data-var='time'>22:02</var> UTC Identified - 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 <var data-var='date'>24</var>, <var data-var='time'>21:53</var> UTC Monitoring - 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 <var data-var='date'>24</var>, <var data-var='time'>21:20</var> UTC Update - 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 <var data-var='date'>24</var>, <var data-var='time'>19:45</var> UTC Investigating - 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.

API returning Error 502 Bad Gateway

May <var data-var='date'>10</var>, <var data-var='time'>16:35</var> UTC Completed - The scheduled maintenance has been completed.May <var data-var='date'> 6</var>, <var data-var='time'>16:36</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.May <var data-var='date'> 6</var>, <var data-var='time'>16:30</var> UTC Scheduled - 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 <var data-var='date'> 6</var>, <var data-var='time'>15:45</var> UTC Completed - The scheduled maintenance has been completed.Apr <var data-var='date'>28</var>, <var data-var='time'>15:45</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr <var data-var='date'>28</var>, <var data-var='time'>15:36</var> UTC Scheduled - 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.

Apr <var data-var='date'>28</var>, <var data-var='time'>15:30</var> UTC Completed - The scheduled maintenance has been completed.Apr <var data-var='date'>26</var>, <var data-var='time'>15:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr <var data-var='date'>26</var>, <var data-var='time'>15:28</var> UTC Scheduled - 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.

Auot-update maintenance

Apr <var data-var='date'>21</var>, <var data-var='time'>17:45</var> UTC Resolved - This incident has been resolved.Apr <var data-var='date'>21</var>, <var data-var='time'>17:00</var> UTC Monitoring - The API is now responding nominally. We will continue to monitor the situation to ensure the cdnjs API remains stable.Apr <var data-var='date'>21</var>, <var data-var='time'>16:30</var> UTC Investigating - 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.

API returning Argo Tunnel error

Apr <var data-var='date'> 7</var>, <var data-var='time'>12:30</var> UTC Completed - The scheduled maintenance has been completed.Apr <var data-var='date'> 6</var>, <var data-var='time'>20:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr <var data-var='date'> 6</var>, <var data-var='time'>19:00</var> UTC Scheduled - 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 maintenance

Nov <var data-var='date'>16</var>, <var data-var='time'>12:55</var> UTC Completed - 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 <var data-var='date'>13</var>, <var data-var='time'>16:55</var> UTC Verifying - 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 <var data-var='date'>12</var>, <var data-var='time'>22:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. This work is expected to last for approximately 24 hours.Nov <var data-var='date'>12</var>, <var data-var='time'>21:55</var> UTC Scheduled - 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.

Aug <var data-var='date'>12</var>, <var data-var='time'>15:26</var> UTC Resolved - At this time we are confident that access to the CDN has been restored for all users of cdnjs.Aug <var data-var='date'>12</var>, <var data-var='time'>14:56</var> UTC Monitoring - A fix has been implemented that should allow users in mainland China to access cdnjs. Cloudflare will continue to monitor the situation.Aug <var data-var='date'>12</var>, <var data-var='time'>11:10</var> UTC Identified - 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 <var data-var='date'>12</var>, <var data-var='time'>10:31</var> UTC Update - 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 <var data-var='date'>12</var>, <var data-var='time'>10:25</var> UTC Investigating - 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.

SSL errors for cdnjs.cloudflare.com

Jun <var data-var='date'>12</var>, <var data-var='time'>12:18</var> UTC Resolved - 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 <var data-var='date'>12</var>, <var data-var='time'>11:15</var> UTC Monitoring - 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 <var data-var='date'>12</var>, <var data-var='time'>10:30</var> UTC Update - The cdnjs API is now correctly responding to library requests, however, we are still working to resolve the issue present on the website.Jun <var data-var='date'>12</var>, <var data-var='time'>09:25</var> UTC Identified - 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 <var data-var='date'>12</var>, <var data-var='time'>08:30</var> UTC Investigating - 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.

cdnjs website & API erroring for some libraries

Apr <var data-var='date'>15</var>, <var data-var='time'>21:50</var> UTC Resolved - 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 <var data-var='date'>15</var>, <var data-var='time'>20:03</var> UTC Monitoring - 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 <var data-var='date'>15</var>, <var data-var='time'>19:28</var> UTC Identified - 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 <var data-var='date'>15</var>, <var data-var='time'>19:01</var> UTC Investigating - 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.

522 & 523 responses for non-cached assets

Dec <var data-var='date'>30</var>, <var data-var='time'>17:19</var> UTC Resolved - We are now confident the fix is working as expected. The cdnjs website and API are now showing libraries and their versions correctly.Dec <var data-var='date'>30</var>, <var data-var='time'>15:35</var> UTC Monitoring - 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 <var data-var='date'>30</var>, <var data-var='time'>15:33</var> UTC Identified - 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 <var data-var='date'>30</var>, <var data-var='time'>09:59</var> UTC Investigating - 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.

Library versions missing from website & API

Jul <var data-var='date'> 2</var>, <var data-var='time'>14:59</var> UTC Resolved - 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 <var data-var='date'> 2</var>, <var data-var='time'>14:17</var> UTC Monitoring - 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 <var data-var='date'> 2</var>, <var data-var='time'>14:02</var> UTC Update - Cloudflare have now raised an incident on their status page due to the outage: https://www.cloudflarestatus.com/incidents/tx4pgxs6zxdrJul <var data-var='date'> 2</var>, <var data-var='time'>13:53</var> UTC Investigating - 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.

502 Bad Gateway

Jun <var data-var='date'>24</var>, <var data-var='time'>13:34</var> UTC Resolved - Cloudflare have confirmed this issue is now resolved and all cdnjs services should be accessible again.Jun <var data-var='date'>24</var>, <var data-var='time'>12:51</var> UTC Monitoring - 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 <var data-var='date'>24</var>, <var data-var='time'>12:37</var> UTC Update - 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 <var data-var='date'>24</var>, <var data-var='time'>11:57</var> UTC Update - 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 <var data-var='date'>24</var>, <var data-var='time'>11:28</var> UTC Identified - 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

Connectivity Issues

Apr <var data-var='date'>15</var>, <var data-var='time'>22:36</var> UTC Resolved - Cloudflare have purged all affected resources from the cache and are confident that this issue has now been resolved.Apr <var data-var='date'>15</var>, <var data-var='time'>20:20</var> UTC Monitoring - 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/cdnjsStatus GitHub: https://github.com/cdnjs/cdnjs/issues/13324Apr <var data-var='date'>15</var>, <var data-var='time'>20:13</var> UTC Identified - Cloudflare have identified the source of the issue and are currently working to roll out a fix to the missing CORS headers.Apr <var data-var='date'>15</var>, <var data-var='time'>19:54</var> UTC Investigating - 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.

Missing CORS Headers

Feb <var data-var='date'> 2</var>, <var data-var='time'>10:00</var> UTC Resolved - 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 <var data-var='date'> 1</var>, <var data-var='time'>23:00</var> UTC Monitoring - 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 <var data-var='date'> 1</var>, <var data-var='time'>21:15</var> UTC Identified - 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 <var data-var='date'> 1</var>, <var data-var='time'>18:30</var> UTC Monitoring - 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 <var data-var='date'> 1</var>, <var data-var='time'>12:00</var> UTC Update - 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 <var data-var='date'> 1</var>, <var data-var='time'>10:30</var> UTC Investigating - 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 <var data-var='date'>28</var>, <var data-var='time'>20:30</var> UTC Resolved - We and Cloudflare are happy to say that the CDN is now performing normally.Dec <var data-var='date'>28</var>, <var data-var='time'>12:00</var> UTC Update - 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 <var data-var='date'>27</var>, <var data-var='time'>12:15</var> UTC Monitoring - 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 <var data-var='date'>26</var>, <var data-var='time'>12:45</var> UTC Update - 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 <var data-var='date'>25</var>, <var data-var='time'>23:30</var> UTC Update - 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 <var data-var='date'>23</var>, <var data-var='time'>18:30</var> UTC Update - 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 <var data-var='date'>23</var>, <var data-var='time'>11:00</var> UTC Identified - 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 <var data-var='date'>22</var>, <var data-var='time'>21:15</var> UTC Update - 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 <var data-var='date'>22</var>, <var data-var='time'>21:00</var> UTC Investigating - 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.

Is cdnjs down?

cdnjs status is UP

Lastest published events

API outage

SRI hashes changed on multiple libraries

API returning 502 responses

cdnjs Services, Components and Regions

Recent cdnjs events

API outage

SRI hashes changed on multiple libraries

API returning 502 responses

Intermittent issues with API responses

API returning Error 502 Bad Gateway

Auto-update bot maintenance

Get your FREE account now,
5 monitors included!

Is cdnjs down?

cdnjs status is UP

Lastest published events

API outage

SRI hashes changed on multiple libraries

API returning 502 responses

cdnjs Services, Components and Regions

Recent cdnjs events

API outage

SRI hashes changed on multiple libraries

API returning 502 responses

Intermittent issues with API responses

API returning Error 502 Bad Gateway

Auto-update bot maintenance

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!