Gemfury incident

Elevated timeouts from NPM-Proxy

Minor Resolved View vendor source →

Gemfury experienced a minor incident on December 15, 2021 affecting Repo endpoints, lasting 51m. The incident has been resolved; the full update timeline is below.

Started
Dec 15, 2021, 03:50 PM UTC
Resolved
Dec 15, 2021, 04:42 PM UTC
Duration
51m
Detected by Pingoru
Dec 15, 2021, 03:50 PM UTC

Affected components

Repo endpoints

Update timeline

  1. investigating Dec 15, 2021, 03:50 PM UTC

    We're seeing elevated timeout error rates from proxied requests to the public NPM registry via npm-proxy.fury.io.

  2. identified Dec 15, 2021, 03:54 PM UTC

    We are receiving sporadic 503 errors from the public npm registry. Status seems to reflect the issue: https://status.npmjs.org

  3. monitoring Dec 15, 2021, 04:07 PM UTC

    NPM-Proxy errors have subsided on our end. We are monitoring this in the context of the still-open npm issue. We're also looking into whether current AWS internet connectivity problems are affecting our service or its dependencies: https://status.aws.amazon.com

  4. resolved Dec 15, 2021, 04:42 PM UTC

    Dependency issues are resolved.