cdnjs Status

@cdnjsStatus

Get the status of the service here or on our site:

GitHub issues for support
Joined February 2019

Tweets

You blocked @cdnjsStatus

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @cdnjsStatus

  1. Jun 12

    📡 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.

    Show this thread
    Undo
  2. Jun 12

    📡 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…

    Show this thread
    Undo
  3. Jun 12

    📡 Identified: The cdnjs API is now correctly responding to library requests, however, we are still working to resolve the issue present on the website.

    Show this thread
    Undo
  4. Jun 12

    📡 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 r…

    Show this thread
    Undo
  5. Jun 12

    📡 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.

    Show this thread
    Undo
  6. Apr 15

    📡 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:

    Show this thread
    Undo
  7. Apr 15

    📡 Monitoring: It would appear the origins for 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…

    Show this thread
    Undo
  8. Apr 15

    📡 Identified: We believe this is due to the ongoing incident Cloudflare has: - Requests to cached assets should work but any request for an asset not cached on cdnjs is likely to fail at present.

    Show this thread
    Undo
  9. Apr 15

    📡 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.

    Show this thread
    Undo
  10. 30 Dec 2019

    📡 Resolved: We are now confident the fix is working as expected. The cdnjs website and API are now showing libraries and their versions correctly.

    Show this thread
    Undo
  11. 30 Dec 2019

    📡 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 pres…

    Show this thread
    Undo
  12. 30 Dec 2019

    📡 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, the…

    Show this thread
    Undo
  13. Retweeted
    2 Dec 2019

    Thanks to who continue to help us every single day and to our other sponsors , , & who provide awesome services for us! 🎉 Most importantly, a big thank you to all of you for using cdnjs! 🧡

    Undo
  14. 2 Jul 2019

    📡 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…

    Show this thread
    Undo
  15. 2 Jul 2019

    📡 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.

    Show this thread
    Undo
  16. 2 Jul 2019

    📡 Investigating: Cloudflare have now raised an incident on their status page due to the outage:

    Show this thread
    Undo
  17. 2 Jul 2019

    📡 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 th…

    Show this thread
    Undo
  18. 24 Jun 2019

    📡 Resolved: Cloudflare have confirmed this issue is now resolved and all cdnjs services should be accessible again.

    Show this thread
    Undo
  19. 24 Jun 2019

    📡 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 follows updates from Cloudflare.

    Show this thread
    Undo
  20. 24 Jun 2019

    📡 Identified: Cloudflare are still working to resolve the route leak that is causing major outages across the internet. Follow their status updates at

    Show this thread
    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·