Dev tools / Package registry / npm

npm

OPERATIONAL

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

CompareStatus page
GradeCLast 90 days
A+PRODCSHIP

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.
90 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
2h 15m
LongestLongest single incident, start to resolved.
5h 57m
Since lastTime since the last counted incident was resolved.
16h 06m

By area

A+Production
0INCIDENTS
0mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90dNothing. Nice.
0 in the last 6 months, 0 in the 6 before.
CShipping
7INCIDENTS
20h 28mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 2Jul 30, 2026 · 4h 24mintermittent Publish Failures
SEV 3Oct 22, 2026 · 5h 16mDegraded Publish, Install, and View Package
SEV 3Oct 22, 2026 · 1h 51mDegraded Package Install and Publishing
Most hit
Package publishing7
Package installation4
www.npmjs.com website2
Replication Feed1
Worse. 10 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 down1
Sev 3 · Can't shipCan't deploy, build or manage it6
Sev 4 · PapercutDocs, status page, slow dashboard2

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 1Sev 1–2

Incident history

Show all 31
Oct 22, 20265h 16mSEV 3
Degraded Publish, Install, and View PackageSev 3 because Package installation had degraded performancewww.npmjs.com website +2
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 3
Degraded Package Install and PublishingSev 3 because Package installation had a partial outagewww.npmjs.com website +2
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 4
Issues with login and viewing packagesSev 4 because www.npmjs.com website had degraded performancewww.npmjs.com website
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 3
Issues with npm package publish and private installSev 3 because Package installation had degraded performancePackage installation +2
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 3
Package Publish DegradationSev 3 because Package publishing had degraded performancePackage publishing
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 PerformanceSev 3 because Package publishing had degraded performancePackage publishing
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 4
npm audits endpoint is having issuesSev 4 from the incident title (no components listed)Security Audit
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 3
Intermittent Failures Impacting npm PublishSev 3 because Package installation had degraded performancePackage installation +1
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 C100.00% up9 incidentsMTTR 2h 15mGitHubGrade F99.87% up50 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)