Is npm down?

The status at the top of this page comes from Hyperping checks of npm, run every minute and refreshed on the page every 60 seconds. Green means the latest checks succeeded; red means they are failing, confirmed from several regions.

We monitor 3 npm services every minute, in turn from Virginia, Frankfurt and Singapore: Registry (registry.npmjs.org, up on a successful response), Search (registry.npmjs.org, up on a successful response) and Login and publish (registry.npmjs.org, up on a 401 response). When a check fails, other regions check again before that service counts as down. npm counts as down when all of them are, and as partly down when only some are. We check what the npm CLI talks to: the registry, its search and its login. The npmjs.com website answers automated checks with a Cloudflare challenge, so it is not checked directly.

An outage can be partial: one feature, one app, one country or one internet provider, and our checks see npm from data centers. Try another network such as mobile data, update or restart the app, and check the official status page for an incident on one feature.

Yes, status.npmjs.org. npm's team updates it by hand, so it can lag behind the start of an outage; our checks run every minute whatever it says.

Yes. Create a free Hyperping account and add registry.npmjs.org as a monitor: you are alerted by email, Slack or your other channels within a minute of a failure. The free plan includes 20 monitors, enough for your own site and the services it depends on.