npm: Intermittent website timeouts and 503's
Timeline of updates
- resolved
Starting at 11:13 UTC our monitoring started reporting increased 503 and timeout rate originating from the website caused by increased crawler traffic. While investigating the issue we discovered that some of our services weren't configured to load balance across database servers, which caused one of them to become overloaded due to increased traffic. We reconfigured our services to alleviate that and saw error and timeout rates drop to base levels around 12:46 UTC.
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-08-03 13:19 UTC, resolved after 0 min, 1 update(s).
- Title
- Intermittent website timeouts and 503's
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/9vwlwf0pfmdm
npm profileRecent npm incidentsAll outages on August 3, 2016npm in August 2016MarkdownJSON