npm Registry

Operational

Official site Provider status

GitHub / npm · Dev Infrastructure

Updated 2026-11-06 12:58 UTC

24h availability

100.00%

0 min down

7d availability

100.00%

0 min down

30d availability

100.00%

0 min down

90d availability

100.00%

0 min down

Period:

Avg response time 34ms

90d: 0 min down, 0 min degraded, 0 min unmeasured

Recent incidents

All incidents Atom feed

No incidents recorded in the lookback window.

Vantage points

Falkenstein, DE Hetzner

202ms Operational

Roubaix, FR OVH

220ms Operational

New York, US DigitalOcean

102ms Operational

Seattle, US Vultr

33ms Operational

Singapore Vultr

222ms Operational

What we monitor

2 active checks

Each row below is one probe-side measurement we run from every vantage point. The availability number on this page is the consensus across these checks, not a single endpoint hit.

HTTP https://registry.npmjs.org/-/ping every minute
TLS registry.npmjs.org:443 every hour

About this data

Availability is measured independently by probes in five locations. Each probe runs the appropriate mix of HTTP, DNS, TLS, and storage checks at per-check cadences and records timing, status code, and any error. A probe votes "up" for a given minute if any of its checks for this service succeeded; the minute is then counted as "up" on the leaderboard only when a strict majority of reporting probes voted up. Minutes where fewer than three probes reported are excluded from the denominator. Full methodology

Embed a badge

Markdown for a README. The image is served by the public API and links back to this page.

          [![npm Registry uptime](https://api.uptimeproject.org/v1/services/npm-registry/badge.svg)](https://uptimeproject.org/service/npm-registry/)

Back to Dev Infrastructure leaderboard