NPM status history
Current state: operational — “All Systems Operational” per https://status.npmjs.org (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do NPM incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-15 17:20 UTC | Package Publish Degradation | resolved | minor | 59 min |
| 2026-09-15 16:13 UTC | Publishing Packages Degraded Performance | resolved | minor | 21 min |
| 2026-09-04 11:29 UTC | npm audits endpoint is having issues | resolved | minor | 2 h 19 min |
| 2026-09-03 21:42 UTC | Intermittent Failures Impacting npm Publish | resolved | minor | 1 h 39 min |
| 2026-07-30 12:06 UTC | intermittent Publish Failures | resolved | minor | 4 h 23 min |
| 2026-07-24 11:08 UTC | Publish and Install failures | resolved | major | 30 min |
| 2026-07-23 16:09 UTC | intermittent Publish and Install Failures | resolved | minor | 3 h 42 min |
| 2026-06-12 12:08 UTC | intermittent Publish Failures | resolved | minor | 48 min |
| 2026-04-29 20:07 UTC | npm website issues | resolved | minor | 42 min |
| 2026-04-29 16:48 UTC | Degraded Performance in View Package and Login on npmjs.com | resolved | minor | 2 h 47 min |
| 2026-04-28 19:55 UTC | npm website degraded service | resolved | minor | 2 h 29 min |
| 2026-04-27 21:06 UTC | npm Website is unavailable | resolved | critical | 1 h 24 min |
| 2026-04-01 10:05 UTC | Increased errors in viewing packages and authentication on npmjs.com | resolved | none | 3 h 06 min |
| 2026-03-31 19:12 UTC | Degraded Performance in View Package and Login on npmjs.com | resolved | minor | 2 h 36 min |
| 2026-03-30 16:41 UTC | delay and errors viewing packages and submitting web based authentication | resolved | minor | 2 h 36 min |
| 2026-03-30 14:54 UTC | delay and errors viewing packages and submitting web based authentication | resolved | minor | 1 h 04 min |
| 2026-03-25 22:39 UTC | Issue with npm website and login. | resolved | major | 46 min |
| 2026-03-05 11:41 UTC | Degraded performance for package publish | resolved | minor | 5 h 54 min |
| 2026-02-25 18:43 UTC | Degraded performance with package installation | resolved | minor | 1 h 20 min |
| 2026-02-17 20:01 UTC | npm publishing impacted | resolved | minor | 2 h 27 min |
| 2026-01-29 20:04 UTC | Degraded Experience Installing and Viewing Packages | resolved | minor | 45 min |
| 2025-12-05 09:02 UTC | Issue connecting to website and registry | resolved | major | 39 min |
| 2025-11-18 13:34 UTC | npmjs.com - Service Disruption | resolved | none | 5 h 36 min |
| 2025-11-06 13:56 UTC | Issue with npm website and login | resolved | minor | 32 min |
| 2025-10-20 17:20 UTC | Issue with package publishing | resolved | minor | 2 h 55 min |
| 2025-10-20 09:31 UTC | Degraded performance of package publish and install | resolved | minor | 4 h 00 min |
| 2025-10-03 18:07 UTC | Degraded performance on npmjs.com | resolved | minor | 7 h 34 min |
| 2025-08-26 12:40 UTC | Degraded Package Install Experience | resolved | minor | 3 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
}