npm said it is investigating an outage affecting the npm website on Apr. 27, 2026. The status page listed the website as a major outage, while package installation, publishing, search, security audit, and replication feed remained operational.
npm said on Apr. 27, 2026 that it was investigating an outage affecting its main website, www.npmjs.com. The update, posted on the company’s status page, listed the issue as a major outage, which means the service is down or severely impaired.
The incident was limited to the website itself, according to the status page. npm said package installation, package publishing, package search, security audit, and the replication feed were all operational when the outage notice was posted.
npm is the main package registry for JavaScript software, so when its website goes down, developers may lose access to package pages and account-related functions. A major outage means the site itself is unavailable or badly broken, even if some behind-the-scenes services still work. This matters because npm is part of the infrastructure many software teams depend on every day.
If your automation depends on npm package metadata, don’t treat the website as a required dependency. Pull package data through the registry APIs or mirror the data you need, and make your workflow tolerant of the website being unavailable. If you run self-hosted build or release automation, separate package installation checks from website-based checks so a site outage does not block your pipeline. Track npm’s status feed or @npmstatus as a signal, but do not build business logic that assumes the public site will always be up.
That separation matters because npm is a core part of the JavaScript software supply chain. Developers use it to find packages, manage accounts, and check package details, while automated tools often rely on the registry and related APIs rather than the marketing or account website.
npm did not say what caused the disruption in the initial incident report. The company’s updates on the status page simply said it was investigating the problem and later continued that investigation, without publishing a cause in the visible incident log.
The status page showed the incident under the Apr. 27 log as “npm Website is unavailable,” and later marked it resolved. It also provides a public view of recent uptime, which showed the website at 99.92% uptime over the past 90 days, while package installation was at 99.98% and the other listed services were at 100.0%.
For users trying to reach package pages or account controls, the outage could mean temporary friction even if package installs kept working. npm also points users to its status updates, the @npmstatus account on Twitter, and feed subscriptions by email, SMS, Atom, or RSS, which is how the company says it notifies people when incidents are created, updated, or resolved.
The incident page suggests the outage was short-lived, but npm has not published a technical root cause in the material now visible on its status site. The next visible step is the company’s post-incident update, if it publishes one, which would explain what failed and whether any follow-up work is planned.
