CheckUpstream measured npm Registry at 100.000% availability across 2053 independent checks (global · registry). 14 incidents were recorded in the past 12 months; the most recent resolved 32 days ago after 5 hours. Status signals are polled from npm Registry's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · registry · n=2053 · p95 251ms (30d)
Share of our own checks against npm Registry endpoints that returned npm Registry's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
npm Registry posted no incidents in this window. That is either a clean run or a communication policy — from outside, the two look identical.
Fewer incidents in the last 30 days than 55% of 232 tracked services.
Share of each window with no impact declared by npm Registry
7d
100.000%
30d
100.000%
90d
99.998%
180d
99.860%
1y
99.931%
Does npm Registry actually matter to you?
A npm Registry outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Jul 30, 12:06 UTC · resolved in 9m · Resolved
Jul 30, 12:06 UTC · resolved in 4h 33m · Resolved
Jul 24, 11:08 UTC · resolved in 31m · Resolved
Live npm Registry status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/npm-registry)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
npm Registry is currently Operational. CheckUpstream tracks npm Registry in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is npm Registry down" view? See the npm Registry Live status page.
Jul 23, 16:09 UTC · resolved in 3h 50m · Resolved
Mar 30, 16:41 UTC · resolved in 2h 45m · Resolved
Mar 30, 14:54 UTC · resolved in 1h 10m · Resolved
Mar 25, 22:39 UTC · resolved in 50m · Resolved
npm Registry's last resolved incident started 32 days ago and lasted 4h 33m (degraded performance).
npm Registry's 30-day measured availability is 100.000%, from CheckUpstream's own probes against npm Registry endpoints. It is the share of checks that returned the expected response, not a figure taken from npm Registry's status page.
Sign up to CheckUpstream and add npm Registry to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll npm Registry's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.