npm: increased timeouts on registry and website
Timeline of updates
- resolved
Between the 3:55 and 4:10 (PDT) an increased rate of 503s was observed on the registry and npmjs.com website. We believe we have isolated the underlying issue and corrected it. We will be looking into adding additional monitoring, to identify this specific category of failure faster.
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 2017-07-13 23:18 UTC, resolved after 0 min, 1 update(s).
- Title
- increased timeouts on registry and website
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/p3ld2xkmt8p2
npm profileRecent npm incidentsAll outages on July 13, 2017npm in July 2017MarkdownJSON