npm Registry Outage Check
Is npm Registry Down Right Now?
✅ npm Registry is up and working normally. Checked: 5:10 PM (GMT+8).
Auto-refreshing live data in 60s
| Component | Status |
|---|---|
| Package installation | Operational |
| Package publishing | Operational |
| Package search | Operational |
| Replication Feed | Operational |
| Security Audit | Operational |
| www.npmjs.com website | Operational |
99.944%
Uptime
60m
MTTR
6.7
Avg Incidents / Mo
90 Days AgoToday
npm Registry Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 32m
Affected: Website, DNS Services
npm Registry API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 40m
Affected: API Requests, API Portal
npm Registry Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 23m
Affected: Website, DNS Services
npm Registry Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 0m
Affected: Website, DNS Services
npm Registry Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 54m
Affected: Core Service, Website
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.
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 60 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.