cdnjs incident

502 Bad Gateway

Critical Resolved View vendor source →

cdnjs experienced a critical incident on July 2, 2019 affecting CDN Service (cdnjs.cloudflare.com) and API (api.cdnjs.com) and 1 more component, lasting 1h 5m. The incident has been resolved; the full update timeline is below.

Started
Jul 02, 2019, 01:53 PM UTC
Resolved
Jul 02, 2019, 02:59 PM UTC
Duration
1h 5m
Detected by Pingoru
Jul 02, 2019, 01:53 PM UTC

Affected components

CDN Service (cdnjs.cloudflare.com)API (api.cdnjs.com)Website (cdnjs.com)

Update timeline

  1. investigating Jul 02, 2019, 01:53 PM UTC

    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.

  2. investigating Jul 02, 2019, 02:02 PM UTC

    Cloudflare have now raised an incident on their status page due to the outage: https://www.cloudflarestatus.com/incidents/tx4pgxs6zxdr

  3. monitoring Jul 02, 2019, 02:17 PM UTC

    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.

  4. resolved Jul 02, 2019, 02:59 PM UTC

    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.