Before you start

Registry metadata, package tarballs and install-script downloads may come from different hosts.

Step by step

  1. Confirm the official entry point through https://docs.npmjs.com/. Avoid unfamiliar sign-in pages.
  2. Use one device and one network exit to open npm; identify whether the home page, sign-in redirect or actual feature fails.
  3. Registry metadata, package tarballs and install-script downloads may come from different hosts.
  4. Check npm config get registry, then npm view npm version. Keep the lockfile when comparing results.
  5. For 401 or 403, check account status and the displayed message before changing network settings.
  6. Change one condition at a time; if an official incident is active, follow the provider’s updates.

Official references

Use these provider resources for current rules. Some announcement links are help pages, not live availability tests.

Common questions

Can switching networks fix every npm error?

No. Account privileges, subscriptions, file permissions and service outages require separate checks.

What should I send to support?

Share the time, client version, redacted error code and minimal reproduction. Never share a password, token, cookie or one-time code.