npm: Service Interruption across public and private repositories.
Timeline of updates
- resolved
This incident has been resolved. Our engineering team was alerted to increased error rates and began to investigate at 9:31 AM ET. Investigation led to some problematic systems configuration with our database. The configuration was rectified which led to partial incident resolution for many npm users and customers, at 9:54 am ET. Follow-up SRE work led to a full restoration of service at 11:06 am ET. We apologize for the inconvenience and are working on post-incident steps to prevent future such issues.
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: none) posted by npm, started 2019-09-26 15:46 UTC, resolved after 0 min, 1 update(s).
- Title
- Service Interruption across public and private repositories.
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/jw2h0k3j6ggh
npm profileRecent npm incidentsAll outages on September 26, 2019npm in September 2019MarkdownJSON