Is npm down right now?
Live npm registry status pulled from status.npmjs.org. Track the npm CLI, the registry API, the website, package signatures, and 2FA. If your `npm install` is hanging or returning 503s, this page will tell you whether the registry itself is the problem before you spend an hour debugging.
Major outage: AWS
npm
OperationalJavaScript registry, install API, web app.
Status from status.npmjs.org · last fetched 1s ago
Developer Platforms
Upstream returned 404
Upstream returned 404
Atlassian source hosting and Pipelines.
Source hosting, Actions, Pages, Packages, Copilot.
macOS / Linux package manager (uses GitHub).
JavaScript registry, install API, web app.
Python Package Index — pip install backend.
AI / ML APIs
Elevated errors for Claude Opus 4.8 — started 24 min ago
FedRAMP workspaces and API orgs have degraded performance — started 1 day ago
Upstream returned invalid JSON
AI code editor — chat, tab, composer.
AI pair programmer — completions, chat, agents.
Gemini API, Vertex AI, AI Studio.
Run open-source ML models via API.
Cloud / Hosting
Service disruption: Increased Error Rates — started 47 days ago
Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. — started 7 days ago
Customers may see incorrect invoice payment status — started 13 hr ago
Upstream returned 404
Upstream returned invalid JSON
Droplets, App Platform, managed databases.
Global app servers, Postgres, volumes.
Azure VMs, App Service, AKS, Azure SQL.
Static + Jamstack hosting, Functions, Forms.
Web services, cron, Postgres, Redis.
Next.js hosting, Edge, Serverless functions.
Databases / Data
Upstream returned 404
Upstream returned invalid JSON
Upstream returned invalid JSON
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain) — started 107 days ago
Serverless MySQL, Vitess-backed.
Postgres, auth, storage, realtime, edge fns.
Payments / Infra
MMS Delivery Failures from a Subset of Twilio Short Codes to Verizon United States — started 3 hr ago
Upstream returned invalid JSON
Upstream returned 404
Upstream returned 404
Developer-first transactional email API.
Transactional + marketing email at scale.
Auth / Identity
Communication
Trouble submitting workflow forms with file attachments on Android. — started 13 hr ago
No public machine-readable feed; consult the official status page.
Voice, video, text servers and DMs.
Service Degradation Affecting Zoom Meeting Recordings — started 1 day ago
Monitoring / Dev Tools
Upstream returned invalid JSON
Upstream returned invalid JSON
APM, infra, logs, RUM, synthetics.
Collaborative design, FigJam, Dev Mode.
Feature flags, experiments, releases.
Error monitoring, performance, replays.
DevZone aggregates publicly available status data and refreshes every 30 seconds. Status indicators reflect each provider’s own machine-readable feed; for incident details and authoritative information, always consult the official status page linked on each card.
npm 90-day incident history
Last 90 days
92.22% incident-free
Quick facts about npm
- npm’s status page is hosted at status.npmjs.org (Statuspage.io).
- GitHub now owns npm — but npm has its own status page, separate from githubstatus.com.
- The registry, the install API, the publish API, and the website are reported as separate components.
- Cloudflare CDN issues often cause partial npm outages even when the origin registry is healthy.
How do I know if it's npm or my own setup?
- `npm ping` — quickest check. A non-200 means the registry is unreachable from your network.
- Try a CDN-bypass mirror: `npm config set registry https://registry.npmjs.cf` (Cloudflare-fronted alternative).
- If installs return 401/403, it’s an auth issue, not an outage. Re-run `npm login`.
- For CI failures, check whether the runner can reach registry.npmjs.org — corporate proxies sometimes block it.
Frequently asked questions
Why is my npm install hanging?
If the dashboard above shows the registry as operational, the issue is likely local: a stale lockfile, a private registry timing out, or your firewall blocking registry.npmjs.org. Try `npm install --verbose` to see exactly which request is stuck. If the registry shows as degraded here, that’s your answer.
How do I know if it’s npm or my private registry?
Run `npm ping --registry=https://registry.npmjs.org`. If that succeeds, public npm is fine and the issue is your `.npmrc` registry override or your private registry server.
Where can I check older npm outages?
Use the 90-day history above for recent incidents. For older history, status.npmjs.org keeps an incident log going back several years.
Does npm have a status API?
Yes — https://status.npmjs.org/api/v2/summary.json. Public, no auth, normalized Statuspage schema.
How long do npm outages typically last?
Recent major outages have lasted 15 minutes to 2 hours. Partial degradations (slow installs, intermittent 5xxs) sometimes persist longer because they are harder to detect.