npm: 403 / 429 Errors for some Users
Timeline of updates
- resolved
Thank you to our users for their reports of success, and patience while engineers from npm and our partners worked together to isolate the cause of this incident. Our content delivery partner investigated as soon as we contacted them and started immediately to deploy a fix, which worked right away. Just now, we took some time to catch up with a handful of users who were experiencing what are now known to be unrelated issues. So, presently we can confirm that the registry is fully functional. We’d like to thank our support and technical staff for their unreserved help on a holiday, and again thank the community for understanding.
From npm’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.npmjs.org (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by npm, started 2020-02-17 12:51 UTC, resolved after 5.1 h, 1 update(s).
- Title
- 403 / 429 Errors for some Users
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/5qxhhcx0vtlc
npm profileRecent npm incidentsAll outages on February 17, 2020npm in February 2020MarkdownJSON