npm Registry Outage Check
Is npm Registry Down Right Now?
✅ npm Registry is up and working normally. Checked: 6:51 PM (GMT+8).
Auto-refreshing live data in 60s
npm Registry's Official Status Page
- npm install and package downloads
- CI/CD build steps that fetch packages
- Yarn and pnpm installs via the npm registry
- Publishing packages to the registry
| Component | Status |
|---|---|
| Package installation | Operational |
| Package publishing | Operational |
| Package search | Operational |
| Replication Feed | Operational |
| Security Audit | Operational |
| www.npmjs.com website | Operational |
SLA Grade: A−
Based on 90-day verified uptime
99.556%
Uptime
51m
Mean Resolution Time (MTTR)
8.3
Avg Incidents / Month
5d ago
Last Incident
90 Days AgoToday
npm Registry Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
npm Registry Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
npm Registry Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
npm Registry Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
npm Registry Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Are you having problems with npm Registry?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns. - 3Check with alternative networkTry loading the site on a mobile cellular network or over a VPN. If it loads, the issue lies in your local ISP provider network routing.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, npm Registry maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 51 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.