npm (npm Registry): SLA evidence report
npm (npm Registry): SLA evidence report
We hold no probe record for npm (npm Registry): we read its status page, so the only incident record here is what npm (npm Registry) declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents npm (npm Registry) declared
- 5
- On its own status page, in this window.
- Window
- 2026-10-08 to 2026-11-07
- UTC, 30 days.
Oct 14, 2026, 9:29 AM UTC to Oct 14, 2026, 11:44 AM UTC
Issues with login and viewing packages, impact minor
Oct 22, 2026, 2:33 AM UTC to Oct 22, 2026, 4:24 AM UTC
Degraded Package Install and Publishing, impact major
Oct 22, 2026, 6:43 AM UTC to Oct 22, 2026, 11:59 AM UTC
Degraded Publish, Install, and View Package, impact minor
Oct 26, 2026, 5:54 AM UTC to Oct 26, 2026, 6:30 AM UTC
View package and auth outage on npmjs.com, impact major
Nov 7, 2026, 2:28 PM UTC to Nov 7, 2026, 3:05 PM UTC
Minor issues impacting package publish, impact minor
Methodology
These incidents come from npm (npm Registry)'s own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit npm (npm Registry) owes, if any, is decided under its own SLA.