Dev tools / Package registry / npm

npm

OPERATIONAL

Since Apr 2024 · 50 incidents · status.npmjs.org · checked just now

CompareStatus page
GradeDLast 90 days
CPRODCSHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a widespread Sev 1 the provider posted itself. A best case.
100.000%Grade C
IncidentsEverything posted on the status page except scheduled maintenance.
40 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
5h 16m
LongestLongest single incident, start to resolved.
5h 57m
Since lastTime since the last counted incident was resolved.
17h 06m

By area

BProduction
2INCIDENTS
11h 13mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 30d
SEV 2Oct 22, 2026 · 5h 16mDegraded Publish, Install, and View Package
SEV 2Sep 27, 2026 · 5h 57mIssues with npm package publish and private install
Most hit
Package installation2
Package publishing2
www.npmjs.com website1
Replication Feed1
Worse. 3 in the last 6 months, 0 in the 6 before.
CShipping
4INCIDENTS
15h 19mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 30d
SEV 2Oct 22, 2026 · 5h 16mDegraded Publish, Install, and View Package
SEV 2Oct 22, 2026 · 1h 51mDegraded Package Install and Publishing
SEV 3Oct 14, 2026 · 2h 15mIssues with login and viewing packages
Most hit
www.npmjs.com website3
Package installation3
Package publishing3
Replication Feed1
Worse. 12 in the last 6 months, 5 in the 6 before.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

Better. 12 in the last 6 months, 16 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down3
Sev 3 · Can't shipCan't deploy, build or manage it1
Sev 4 · PapercutDocs, status page, slow dashboard0

When it breaks

Start times, last 12 months, UTC.

What breaks

www.npmjs.com website16 incidents
Package publishing13 incidents
Package installation9 incidents
Replication Feed2 incidents
Security Audit2 incidents
Package search1 incident

Communication

Updates eachStatus page updates per incident, on average.
3.8Last 12 months
Update gapMedian time between status page updates during an incident.
32mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 6Sev 1–2

Incident history

Show all 31
Oct 22, 20265h 16mSEV 2
Degraded Publish, Install, and View PackagePackage install, publish and website viewing were degraded for about five hours; the text gives no scope or error rate.AI-graded · www.npmjs.com website +2
Why this grade
  1. RULES · SEV 3
    Sev 3 because Package installation had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Package install, publish and website viewing were degraded for about five hours; the text gives no scope or error rate.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
3 updates
  1. 06:43 UTC · investigating
    We are currently investigating this issue.
  2. 09:00 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 11:59 UTC · resolved
    This incident has been resolved.
Source
Oct 22, 20261h 51mSEV 2
Degraded Package Install and Publishingnpm package installation and publishing were degraded from about 02:33 to 04:24 UTC on October 22, 2026, with the website also affected. The updates identify the issue and say a fix was implemented, but do not describe the cause or the number of users hit.AI-graded · www.npmjs.com website +2
Why this grade
  1. RULES · SEV 3
    Sev 3 because Package installation had a partial outage
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Package installation and publishing were degraded for about 2 hours, with partial outage; the scope is not specified in the update text.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
5 updates
  1. 02:33 UTC · investigating
    We are currently investigating this issue.
  2. 02:37 UTC · investigating
    We are continuing to investigate this issue.
  3. 03:07 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 04:10 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 04:24 UTC · resolved
    This incident has been resolved.
Source
Oct 14, 20262h 15mSEV 3
Issues with login and viewing packagesnpm's website had increased errors and latency for logins, package viewing, and package settings from about 09:29 to 11:44 UTC on 14 October 2026. Login and settings access were the most affected. The text gives no scope, and the resolution details are not described beyond a fix being implemented and monitored.AI-graded · www.npmjs.com website
Why this grade
  1. RULES · SEV 4
    Sev 4 because www.npmjs.com website had degraded performance
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Website login and package settings saw elevated errors and latency for about two hours; package viewing was also slow, and the text does not say how widely.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
5 updates
  1. 09:29 UTC · investigating
    We observed increased errors and latency in login and viewing packages. We are investigating the issue.
  2. 11:06 UTC · investigating
    We are continuing to investigate the issue. We also observe increased errors in accessing package settings.
  3. 11:20 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 11:33 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 11:44 UTC · resolved
    This incident has been resolved.
Source
Sep 27, 20265h 57mSEV 2
Issues with npm package publish and private installPackage publishing and private package installs were degraded for about six hours; the cause and blast radius were not described.AI-graded · Package installation +2
Why this grade
  1. RULES · SEV 3
    Sev 3 because Package installation had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Package publishing and private package installs were degraded for about six hours; the cause and blast radius were not described.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
3 updates
  1. 00:50 UTC · investigating
    We are currently investigating this issue.
  2. 01:30 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 06:47 UTC · resolved
    This incident has been resolved.
Source
Sep 15, 20261h 00mSEV 2
Package Publish Degradationnpm package publishing was degraded from about 17:20 to 18:19 UTC on 2026-09-15. The provider said the issue was identified and a fix was implemented, then marked it resolved. No further detail on cause or number of affected users was given.AI-graded · Package publishing
Why this grade
  1. RULES · SEV 3
    Sev 3 because Package publishing had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Package publishing was degraded for about an hour; the update text gives no error rate or affected share.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
4 updates
  1. 17:20 UTC · investigating
    We are currently investigating this issue.
  2. 17:20 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 18:18 UTC · identified
    Stable
  4. 18:19 UTC · resolved
    This incident has been resolved.
Source
Sep 15, 202622mSEV 3
Publishing Packages Degraded PerformancePackage publishing was degraded, with some new versions slow to become available, for about 22 minutes before resolution.AI-graded · Package publishing
Why this grade
  1. RULES · SEV 3
    Sev 3 because Package publishing had degraded performance
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Package publishing was degraded, with some new versions slow to become available, for about 22 minutes before resolution.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
2 updates
  1. 16:13 UTC · investigating
    We are investigating delays affecting npm package publishing. Some newly published package versions may take longer than expected to become available.
  2. 16:35 UTC · resolved
    This incident has been resolved.
Source
Sep 4, 20262h 20mSEV 3
npm audits endpoint is having issuesThe npm security audit endpoint was degraded for about two hours; the text gives no error rate or scope.AI-graded · Security Audit
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · LOW CONFIDENCE
    The npm security audit endpoint was degraded for about two hours; the text gives no error rate or scope.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
3 updates
  1. 11:29 UTC · investigating
    We are currently investigating this issue.
  2. 13:27 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 13:48 UTC · resolved
    This incident has been resolved.
Source
Sep 3, 20261h 39mSEV 2
Intermittent Failures Impacting npm Publishnpm had intermittent failures affecting package publishing and package installation starting 21:42 UTC and resolved at 23:21 UTC on 2026-09-03. A fix was implemented and monitored before resolution. The update text gives no further cause or affected share.AI-graded · Package installation +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Package installation had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Intermittent failures hit npm publishing and package installation for about 1.5 hours; the scope and failure rate were not specified.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
4 updates
  1. 21:42 UTC · investigating
    We are currently investigating this issue.
  2. 22:17 UTC · investigating
    We are continuing to investigate this issue.
  3. 22:41 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 23:21 UTC · resolved
    This incident has been resolved.
Source
Jul 30, 20264h 24mSEV 2
intermittent Publish FailuresPackage publishing to npm failed intermittently for about four hours; the text does not say how many publishers were hit.AI-graded · Package publishing
Why this grade
  1. RULES · SEV 3
    Sev 3 because Package publishing had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Package publishing to npm failed intermittently for about four hours; the text does not say how many publishers were hit.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
3 updates
  1. 12:06 UTC · investigating
    We are currently investigating this issue.
  2. 15:21 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 16:30 UTC · resolved
    This incident has been resolved.
Source
Jul 24, 202631mSEV 3
Publish and Install failuresSev 3 because Package installation had a partial outagePackage installation +1
4 updates
  1. 11:08 UTC · investigating
    We are currently investigating this issue.
  2. 11:32 UTC · investigating
    We are continuing to investigate this issue.
  3. 11:36 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 11:38 UTC · resolved
    This incident has been resolved.
Source
Jul 23, 20263h 43mSEV 3
intermittent Publish and Install FailuresSev 3 because Package installation had degraded performancePackage installation +1
3 updates
  1. 16:09 UTC · investigating
    We are currently investigating this issue.
  2. 18:04 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 19:52 UTC · resolved
    This incident has been resolved.
Source
Jun 12, 202648mSEV 3
intermittent Publish FailuresSev 3 because Package publishing had degraded performancePackage publishing
4 updates
  1. 12:08 UTC · investigating
    We are currently investigating this issue.
  2. 12:33 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 12:44 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 12:57 UTC · resolved
    This incident has been resolved.
Source
Apr 29, 202642mSEV 4
npm website issuesSev 4 because www.npmjs.com website had degraded performancewww.npmjs.com website
3 updates
  1. 20:07 UTC · investigating
    We are currently investigating this issue.
  2. 20:49 UTC · investigating
    We are continuing to investigate this issue.
  3. 20:49 UTC · resolved
    This incident has been resolved.
Source
Apr 29, 20262h 47mSEV 4
Degraded Performance in View Package and Login on npmjs.comSev 4 because www.npmjs.com website had degraded performancewww.npmjs.com website
3 updates
  1. 16:48 UTC · investigating
    We are currently investigating this issue.
  2. 18:47 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 19:35 UTC · resolved
    This incident has been resolved.
Source
Apr 28, 20262h 30mSEV 4
npm website degraded serviceSev 4 because www.npmjs.com website had degraded performancewww.npmjs.com website
3 updates
  1. 19:55 UTC · investigating
    We are currently investigating this issue.
  2. 21:04 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 22:24 UTC · resolved
    This incident has been resolved.
Source
Apr 27, 20261h 24mSEV 4
npm Website is unavailableSev 4 because www.npmjs.com website had a major outagewww.npmjs.com website
3 updates
  1. 21:06 UTC · investigating
    We are currently investigating this issue.
  2. 22:28 UTC · investigating
    We are continuing to investigate this issue.
  3. 22:30 UTC · resolved
    This incident has been resolved.
Source
Apr 1, 20263h 07mSEV 4
Increased errors in viewing packages and authentication on npmjs.comSev 4 because www.npmjs.com website had degraded performancewww.npmjs.com website
3 updates
  1. 10:05 UTC · investigating
    We are observing increased errors in viewing packages and authentication on npmjs website. We are investigating this issue.
  2. 12:20 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 13:12 UTC · resolved
    This incident has been resolved.
Source
Mar 31, 20262h 37mSEV 4
Degraded Performance in View Package and Login on npmjs.comSev 4 because www.npmjs.com website had degraded performancewww.npmjs.com website
4 updates
  1. 19:12 UTC · investigating
    We are seeing degraded performance in package viewing and authentication on npmjs website. We are currently investigating the issue.
  2. 20:42 UTC · investigating
    We have implemented initial fixes and are continuing to investigate this issue
  3. 21:12 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 21:49 UTC · resolved
    This incident has been resolved.
Source
Mar 30, 20262h 36mSEV 4
delay and errors viewing packages and submitting web based authenticationSev 4 because www.npmjs.com website had degraded performancewww.npmjs.com website
4 updates
  1. 16:41 UTC · investigating
    We are currently investigating this issue.
  2. 17:56 UTC · investigating
    We have implemented some initial fixes. We are continuing to investigate the issue.
  3. 18:19 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 19:17 UTC · resolved
    This incident has been resolved.
Source
Mar 30, 20261h 04mSEV 4
delay and errors viewing packages and submitting web based authenticationSev 4 because www.npmjs.com website had degraded performancewww.npmjs.com website
4 updates
  1. 14:54 UTC · investigating
    We are currently investigating this issue.
  2. 15:17 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 15:30 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 15:59 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
Docker HubGrade A+100.00% up4 incidentsMTTR 11mnpmGrade D100.00% up9 incidentsMTTR 2h 15mGitHubGrade F99.87% up49 incidentsMTTR 1h 18m

README badge

npm's live grade, for your README.

npm grade badge
[![npm on downagain.dev](https://downagain.dev/badge/npm.svg)](https://downagain.dev/p/npm)