npm: Increased 503 rate on tarball downloads served from Sydney
Timeline of updates
- resolved
The 503 rate has returned to nominal levels.
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 2016-09-28 04:59 UTC, resolved after 46 min, 1 update(s).
- Title
- Increased 503 rate on tarball downloads served from Sydney
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/xmxgp5l7ljk5
npm profileRecent npm incidentsAll outages on September 28, 2016npm in September 2016MarkdownJSON