registry.npmjs.org logo

npm Registry status

Current status
Up and running
No spike in reports
Response time
38 ms
Uptime (24h)
100.00%
rimetry Health Score
99.00/ 100Excellent
Reliability snapshot

npm Registry uptime & performance at a glance

Current status
Operational
Uptime · 24h
100%
Uptime · 7 days
100%
Uptime · 30 days
100%
Response time
38 ms
Baseline 199 ms
Tracked incidents
0
SSL certificate
—
Independent check rounds

Is npm Registry down, or is it just you?

Multiple independent check rounds from rimetry's monitoring infrastructure, run seconds apart.

Our checks reached npm Registry successfully in every round of the last check cycle.

Check roundLast checkSuccess rate (24h)Avg response
Round 1Reachable100%487 ms
Round 2Reachable100%412 ms
Round 3Reachable100%373 ms
Round 4Reachable100%387 ms

Based on 3,272 automated checks in the last 24 hours. Each round is an independent pass over the same endpoint, seconds apart — a single failing round is not an outage; repeated failures across rounds are.

What can be affected

What can be affected on npm Registry?

These are the main npm Registry functions that can experience separate issues.

  • Website
    Open the site in another browser to rule out a local cache issue
  • API
    Check whether the API behaves differently from the web interface
  • Downloads
    Check whether offline downloads still play while streaming fails
  • Search
    Try a simpler query — search can fail while the rest works

This list shows which parts can fail on their own. It does not mean any of them is failing right now — the live status above is the only claim we make about the current state.

Incident timeline

No incidents reported. Everything is green.

AI summary

npm Registry appears stable across all monitored regions. Community reports in the last hour are within normal noise levels.

0 reports in the last hour
Community signal
Monitoring live signals…
10 min
Not enough data yet
1 hour
Not enough data yet
Countries
Not enough data yet
Reports over 24h

Monitoring live signals…

By issue type

No disruptions detected

By country

No regional issues yet

About npm Registry

The npm Registry is a comprehensive database and distribution platform for JavaScript packages used by developers to manage software dependencies. It is essential for executing package installations, publishing new versions, and running automated CI/CD builds that require external modules. Users generally observe problems when the search function fails, or when the registry returns 500-series errors during a command-line installation. A registry outage can block entire development pipelines by preventing the retrieval of critical code libraries. Rimetry monitors the health and response speed of these package endpoints to ensure developers know when the registry is experiencing technical difficulties.

Problems with npm Registry can affect website, api, downloads independently.

npm Registry (registry.npmjs.org) is a developer tools service monitored continuously by rimetry's automated checks. We probe its public endpoints every 60 seconds in repeated independent rounds to detect outages and latency spikes the moment they happen.

Right now npm Registry is reporting as operational across our probes, with an average response time of 38 ms and 100.00% uptime over the last 24 hours. Most users connecting to registry.npmjs.org are seeing it work normally.

Common causes of disruption for services like npm Registry include backend API failures, region-specific routing problems at the CDN or ISP layer, expired TLS certificates, DNS misconfigurations, and capacity spikes during major events. rimetry combines automated probes, vendor status feeds, and verified community reports to give you a single high-confidence answer instead of guessing.

Share or embed live status

Paste this anywhere — your site, docs, README — and visitors see the live rimetry health for this service.

HTML / iframe
<iframe src="https://rimetry.com/embed/npm" title="npm Registry status — rimetry" width="320" height="72" frameborder="0" loading="lazy" referrerpolicy="no-referrer-when-downgrade" style="border:0;overflow:hidden;color-scheme:dark"></iframe>
<p style="font:11px -apple-system,sans-serif"><a href="https://rimetry.com/npm-status?utm_source=embed&utm_medium=badge&utm_campaign=service-status&utm_content=npm" rel="dofollow">npm Registry status by rimetry</a></p>
Markdown
[![npm Registry status](https://rimetry.com/api/badge/service/npm.svg)](https://rimetry.com/npm-status?utm_source=embed&utm_medium=badge&utm_campaign=service-status&utm_content=npm)
Markdown — card
[![npm Registry status](https://rimetry.com/api/badge/service/npm/card.svg)](https://rimetry.com/npm-status?utm_source=embed&utm_medium=badge&utm_campaign=service-status&utm_content=npm)
More in Developer Tools

Other developer tools tools people watch alongside npm Registry. See the full category.

What is npm Registry?

Node.js package registry.

npm Registry is part of our Developer Tools category. You can also review current trending outages across the internet.

Common issues

  • · Elevated API error rates or timeouts
  • · Builds and deployments queuing or failing
  • · Dashboard slow or unavailable
  • · Webhook deliveries delayed

Similar patterns often surface across other developer tools providers — cross-check against the global outage map.

Troubleshooting

  • · Open the site in another browser to rule out a local cache issue
  • · Check whether the API behaves differently from the web interface
  • · Check whether offline downloads still play while streaming fails
  • · Try a simpler query — search can fail while the rest works
  • · Check your own error rate and status codes before assuming a platform outage
  • · Retry with exponential backoff — 429 and 5xx are often short-lived
  • · Confirm the token or API key hasn't expired or been rotated
  • · Test from a different network or region to rule out routing
  • · Compare the API and the dashboard: they can degrade independently
  • · Check npm Registry's official social channels

Not sure whether it's you or the service? Run a live speed test, check what your IP looks like from the edge, or watch for regional trouble on the worldwide outage map. For the wider picture, browse recent incidents or filter down to developer tools.

FAQ

  • Is npm Registry down for everyone?
    Use the live status above — green means it's likely just you.
  • How often is the status updated?
    Every minute from four global regions.
  • Is npm Registry Website down?
    Website can fail on its own, separately from the rest of npm Registry. Compare the live status above with your own test of that specific function.
  • Where can I see past npm Registry incidents?
    Every event we've recorded lives in the live incident feed, and older ones are grouped in the monthly incident archive.
  • What else is broken right now?
    See the trending outages page or narrow it to developer tools.