Drumbeats

Is it down? › Developer infrastructure

Is npm down?

Live status for npmjs.com from Drumbeats' own probes, with 8-day uptime, outage history and npm's official status feed.

npm is up

Last checked from Europe at (HTTP 200 in 423 ms).

This checks the npm registry itself (the endpoint `npm install` talks to), not the npmjs.com website.

Last check: from Europe · 423 ms · HTTP 200. Refreshes every 5 minutes.

What we check: GET https://registry.npmjs.org/-/ping every 5 minutes, expecting HTTP 200. A failure is only reported after a second region and a 30-second re-check agree.

Uptime and downtime

Last 24 hours
100.00%
0 incidents · 0 min down
Last 7 days
100.00%
0 incidents · 0 min down · 1 unverified
Last 30 days8 of 30 days measured
100.00%
0 incidents · 0 min down · 1 unverified
Last 365 days8 of 365 days measured
100.00%
0 incidents · 0 min down · 1 unverified

Uptime is (successful checks ÷ all counted checks) over our own scheduled checks from Europe. Downtime is sample-derived at the same 5-minute resolution: every confirmed failed check counts as 5 minutes of downtime, except isolated blips, which count against uptime but not against downtime or the incident count. Blocked or unconfirmed checks are excluded rather than guessed.

No downtimeSome downtimeSignificant downtimeData gap

Response time

800 ms400 ms010-11 10:00 UTC10-12 09:00 UTC
Median response 357 msSlowest p95 755 msChecks 278
2800 ms1400 ms010-05 10:00 UTC10-12 09:00 UTC
Median response 368 msSlowest p95 2764 msChecks 2005
2800 ms1400 ms009-13 UTC10-12 UTC
Median response 366 msSlowest p95 2764 msChecks 2180

Amber line: median (p50) of successful checks per hour (per day on the 30-day view). Thin line: p95. Measured from Europe; a single vantage point, so treat the absolute numbers as relative.

Outage history from our checks

A blip is a single confirmed failed check with successful checks either side; it appears here but is excluded from the incident count and the downtime figure above (it still counts against the uptime percentage). Durations are quantised to our 5-minute check interval, so they usually read slightly longer than the vendor's own figures.

Official status from npm

Source: status.npmjs.org, refreshed every 10 minutes. These entries are npm's own reports, not our findings. The gap between our probes failing and the vendor acknowledging it is usually the moment you are searching.

It says up, but you still can't reach npm?

A global check passing and your request failing are not contradictory. Work outward from your machine:

  1. Try another network. Switch to mobile data or a phone hotspot. If it works there, the problem is your office/home network, VPN or corporate proxy, not npm.
  2. Disconnect your VPN. Corporate and consumer VPNs exit from IP ranges that get rate-limited or blocked by bot protection; npm may be refusing that exit node specifically.
  3. Flush your DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS, resolvectl flush-caches on systemd Linux) or point your resolver at 1.1.1.1 / 8.8.8.8 temporarily.
  4. Check your clock. TLS handshakes fail with confusing errors when the system time is minutes off.
  5. Check the region. Our probes run from Europe and US East. A CDN or regional edge failure elsewhere can affect you and not us. Try our website down checker against the exact URL you are using.
  6. Check whether it's your account, not the service. API keys expiring, quota limits and suspended workspaces produce 401/403/429 responses that look like outages from inside an app.

Frequently asked questions

Is npm down right now?

npm is up. Last checked from Europe at 09:25 UTC (HTTP 200 in 423 ms). This verdict comes from Drumbeats' own automated checks, run every 5 minutes from Europe and confirmed from US East before any failure is reported.

What exactly does Drumbeats check for npm?

We send a GET request to https://registry.npmjs.org/-/ping and expect HTTP 200. This checks the npm registry itself (the endpoint `npm install` talks to), not the npmjs.com website.

Why do your outage durations differ from npm's own status page?

We sample every 5 minutes, so our durations are quantised to 5-minute steps and the shortest outage we can observe is one check interval. npm's own numbers come from internal monitoring with far finer resolution, and vendors often start the clock when they acknowledge an incident rather than when it began. Both views are shown on this page, clearly separated.

Is this page affiliated with npm?

No. Drumbeats is not affiliated with, endorsed by or a partner of npm. This page reflects independent automated checks from our own infrastructure, plus incidents npm publishes on its own status page, shown separately and linked to the source.

How checks, confirmation, blips and uptime work is explained once on the hub page.

Is Cloudflare down? Is Docker Hub down? Is GitHub down? Is Stripe down? Is Vercel down? All services →

Monitor your own services the same way

Uptime checks from multiple regions, cron and background-job heartbeats, and alerts to Slack, email or webhooks. Free for up to 50 monitors.

Start monitoring free