cdnjs incident

522 & 523 responses for non-cached assets

Major Resolved View vendor source →

cdnjs experienced a major incident on April 15, 2020 affecting CDN Service (cdnjs.cloudflare.com), lasting 2h 48m. The incident has been resolved; the full update timeline is below.

Started
Apr 15, 2020, 07:01 PM UTC
Resolved
Apr 15, 2020, 09:50 PM UTC
Duration
2h 48m
Detected by Pingoru
Apr 15, 2020, 07:01 PM UTC

Affected components

CDN Service (cdnjs.cloudflare.com)

Update timeline

  1. investigating Apr 15, 2020, 07:01 PM UTC

    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.

  2. identified Apr 15, 2020, 07:28 PM UTC

    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.

  3. monitoring Apr 15, 2020, 08:03 PM UTC

    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/2VbxQ96

  4. resolved Apr 15, 2020, 09:50 PM UTC

    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/2VbxQ96