npm is the world's largest software registry for JavaScript packages.
Real-time check from multiple global locations
--
Response Time
--
Status Code
--
Region
Use our status checker above to confirm whether the issue is with npm or your local connection.
Visit npm's status page for official updates, or see our npm Status Page guide.
Get instant alerts for future npm outages with PerkyDash's free uptime monitoring.
If your app depends on npm, create an emergency status page to keep your users informed.
Set up free monitoring for npm and get instant alerts via email, Slack, or webhooks when it goes down.
npm install failures during outages typically show ETIMEDOUT or ENOTFOUND errors. Check our status above to verify npm registry availability. If npm is up, try clearing your npm cache with 'npm cache clean --force' and check your network connection.
If packages are in your node_modules or npm cache, you can work offline. Consider using npm ci for CI/CD which uses package-lock.json. For better reliability, you can set up a private registry mirror or use Verdaccio as a caching proxy.
Publishing failures can occur during npm outages or due to authentication issues. Verify npm status above, check your npm login with 'npm whoami', and ensure your package name isn't taken. Publishing typically requires the registry write endpoint to be available.
Yes, npm outages can cause CI/CD builds to fail during dependency installation. Consider using package caching in your CI (GitHub Actions, GitLab CI), or set up a private npm proxy/mirror for critical production builds.