Vendor Status Watch

← all vendors

NPM status history

Current state: operational — “All Systems Operational” per https://status.npmjs.org (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

4incidents, last 30 days
7incidents, last 90 days
28incidents on record
Incidents per week, last 12 weeks:

How long do NPM incidents last?

2.4 hmedian incident duration28 measured
4.4 h90th percentile1 in 10 ran longer
42 minmedian, major/critical only4 incidents

From 28 incidents with a vendor-posted start and resolve time. Longest on record: Degraded performance on npmjs.com — 7.6 h (2025-10-03 18:07 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (28)

StartedIncidentStatusImpactDuration
2026-09-15 17:20 UTCPackage Publish Degradationresolvedminor59 min
2026-09-15 16:13 UTCPublishing Packages Degraded Performanceresolvedminor21 min
2026-09-04 11:29 UTCnpm audits endpoint is having issuesresolvedminor2 h 19 min
2026-09-03 21:42 UTCIntermittent Failures Impacting npm Publishresolvedminor1 h 39 min
2026-07-30 12:06 UTCintermittent Publish Failuresresolvedminor4 h 23 min
2026-07-24 11:08 UTCPublish and Install failuresresolvedmajor30 min
2026-07-23 16:09 UTCintermittent Publish and Install Failuresresolvedminor3 h 42 min
2026-06-12 12:08 UTCintermittent Publish Failuresresolvedminor48 min
2026-04-29 20:07 UTCnpm website issuesresolvedminor42 min
2026-04-29 16:48 UTCDegraded Performance in View Package and Login on npmjs.comresolvedminor2 h 47 min
2026-04-28 19:55 UTCnpm website degraded serviceresolvedminor2 h 29 min
2026-04-27 21:06 UTCnpm Website is unavailableresolvedcritical1 h 24 min
2026-04-01 10:05 UTCIncreased errors in viewing packages and authentication on npmjs.comresolvednone3 h 06 min
2026-03-31 19:12 UTCDegraded Performance in View Package and Login on npmjs.comresolvedminor2 h 36 min
2026-03-30 16:41 UTCdelay and errors viewing packages and submitting web based authenticationresolvedminor2 h 36 min
2026-03-30 14:54 UTCdelay and errors viewing packages and submitting web based authenticationresolvedminor1 h 04 min
2026-03-25 22:39 UTCIssue with npm website and login.resolvedmajor46 min
2026-03-05 11:41 UTCDegraded performance for package publishresolvedminor5 h 54 min
2026-02-25 18:43 UTCDegraded performance with package installationresolvedminor1 h 20 min
2026-02-17 20:01 UTCnpm publishing impactedresolvedminor2 h 27 min
2026-01-29 20:04 UTCDegraded Experience Installing and Viewing Packagesresolvedminor45 min
2025-12-05 09:02 UTCIssue connecting to website and registryresolvedmajor39 min
2025-11-18 13:34 UTCnpmjs.com - Service Disruptionresolvednone5 h 36 min
2025-11-06 13:56 UTCIssue with npm website and loginresolvedminor32 min
2025-10-20 17:20 UTCIssue with package publishingresolvedminor2 h 55 min
2025-10-20 09:31 UTCDegraded performance of package publish and installresolvedminor4 h 00 min
2025-10-03 18:07 UTCDegraded performance on npmjs.comresolvedminor7 h 34 min
2025-08-26 12:40 UTCDegraded Package Install Experienceresolvedminor3 h 09 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch NPM with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "npm"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}