npm: Elevated 503s for users near Amsterdam
Timeline of updates
- resolved
A single machine testing a kernel upgrade was responsible for the unusual errors. It has been pulled out of rotation.
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 2015-05-11 15:26 UTC, resolved after 41 min, 1 update(s).
- Title
- Elevated 503s for users near Amsterdam
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/bbd998rhfbfm
npm profileRecent npm incidentsAll outages on May 11, 2015npm in May 2015MarkdownJSON