All services / Developer tools

npm registry

Current assessment
Operational (provider)
Confidence
High confidence
Scope
Provider-wide
Last verified
Oct 25, 01:36 AM UTC
Sources
OfficialKorantix

Official incident history

  1. Degraded Publish, Install, and View Package

    Started: · Duration: 316 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  2. Degraded Package Install and Publishing

    Started: · Duration: 111 min
    Provider updates (4)
    1. Investigating “We are currently investigating this issue.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

  3. Issues with login and viewing packages

    Started: · Duration: 135 min
    Provider updates (4)
    1. Investigating “We observed increased errors and latency in login and viewing packages. We are investigating the issue.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

  4. Issues with npm package publish and private install

    Started: · Duration: 357 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  5. Package Publish Degradation

    Started: · Duration: 60 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Resolved “This incident has been resolved.”
    Resolved

  6. Publishing Packages Degraded Performance

    Started: · Duration: 22 min
    Provider updates (2)
    1. Investigating “We are investigating delays affecting npm package publishing. Some newly published package versions may take longer than expected to become available.”
    2. Resolved “This incident has been resolved.”
    Resolved

  7. npm audits endpoint is having issues

    Started: · Duration: 140 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  8. Intermittent Failures Impacting npm Publish

    Started: · Duration: 99 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  9. intermittent Publish Failures

    Started: · Duration: 264 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  10. Publish and Install failures

    Started: · Duration: 31 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  11. intermittent Publish and Install Failures

    Started: · Duration: 223 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  12. intermittent Publish Failures

    Started: · Duration: 48 min
    Provider updates (4)
    1. Investigating “We are currently investigating this issue.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

  13. npm website issues

    Started: · Duration: 42 min
    Provider updates (2)
    1. Investigating “We are currently investigating this issue.”
    2. Resolved “This incident has been resolved.”
    Resolved

  14. Degraded Performance in View Package and Login on npmjs.com

    Started: · Duration: 167 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  15. npm website degraded service

    Started: · Duration: 150 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  16. npm Website is unavailable

    Started: · Duration: 84 min
    Provider updates (2)
    1. Investigating “We are currently investigating this issue.”
    2. Resolved “This incident has been resolved.”
    Resolved

  17. Increased errors in viewing packages and authentication on npmjs.com

    Started: · Duration: 187 min
    Provider updates (3)
    1. Investigating “We are observing increased errors in viewing packages and authentication on npmjs website. We are investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  18. Degraded Performance in View Package and Login on npmjs.com

    Started: · Duration: 157 min
    Provider updates (3)
    1. Investigating “We are seeing degraded performance in package viewing and authentication on npmjs website. We are currently investigating the issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  19. delay and errors viewing packages and submitting web based authentication

    Started: · Duration: 156 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  20. delay and errors viewing packages and submitting web based authentication

    Started: · Duration: 64 min
    Provider updates (4)
    1. Investigating “We are currently investigating this issue.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
npm Status ↗ · All Systems Operational · Oct 25, 01:36 AM UTC
Korantix
HTTP 200 · 944 ms · Oct 25, 01:34 AM UTC

Why this assessment

  • Provider reports no active incident.
  • Korantix reached the endpoint (HTTP 200, 944 ms). This only shows that the endpoint answered.
  • 944 ms is within this service's usual range (median 545 ms, p95 896 ms over 656 checks).

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official4 min agoYes — recent
Korantix6 min agoYes — recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗