npm: Increased 503 rates
Timeline of updates
- resolved
We confirmed that 503 rates have dropped down to base levels for an extended period of time. No root cause has been determined yet, but we will continue investigating.
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 2016-07-25 13:19 UTC, resolved after 3.8 h, 1 update(s).
- Title
- Increased 503 rates
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/7vyshjllh5x6
npm profileRecent npm incidentsAll outages on July 25, 2016npm in July 2016MarkdownJSON