npm: 503s on www
Timeline of updates
- resolved
We have deployed a hot fix for the issue and 503s have been resolved. Download counts may not be available for all packages. We are working on a longer-term solution. Update: we have deployed a better fix and download counts are once again available for all packages.
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 2014-12-11 01:25 UTC, resolved after 7 min, 1 update(s).
- Title
- 503s on www
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/b0x921vff71v
npm profileRecent npm incidentsAll outages on December 11, 2014npm in December 2014MarkdownJSON