npm Status
System status
View historical uptime →Incident overview
Total incidents
9
Active now
0
Resolved
9
Avg. resolution
2h 28m
Recent incidents
View all →Issues with login and viewing packages
Issues with npm package publish and private install
Package Publish Degradation
Publishing Packages Degraded Performance
npm audits endpoint is having issues
Intermittent Failures Impacting npm Publish
intermittent Publish Failures
Publish and Install failures
intermittent Publish and Install Failures
Frequently asked questions
Is npm down right now?
npm is currently operational. DevHelm monitors npm's official status page continuously and updates this page every 5 minutes.
What is npm's current uptime?
npm has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from npm's official status page data.
How many incidents has npm had recently?
npm has experienced 9 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 2h 28m. All incidents are currently resolved.
What components does npm monitor?
DevHelm tracks 6 individual components for npm, including www.npmjs.com website, Package installation, Package publishing, Package search, Security Audit, and 1 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about npm outages?
You can subscribe to npm's incident feed via Atom/RSS at devhelm.io/status/npm/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add npm as a dependency in your DevHelm workspace.
What SLA does npm offer?
See the full npm SLA report at devhelm.io/sla/npm — including their official uptime guarantee, pricing tiers, credit policy, and how their measured uptime compares to their SLA commitment.
About npm status monitoring
This page provides real-time operational status for npm, powered by DevHelm's continuous monitoring infrastructure. We track npm's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
npm status data is refreshed every 5 minutes. We currently track 6 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track npm in your stack
Get alerted when npm has issues — before your users notice. Set up in 30 seconds.