npm: Increased 503 rates for EU users requesting scoped packages
Timeline of updates
- resolved
At around 14:10 UTC our monitoring alerted us of increased registry 503 rates. We've isolated the issue to our EU region and identified the cause to be a misconfiguration of our deployment stack on one of the servers in that region. The issue was resolved around 14:55 UTC. We've since taken additional steps in order to ensure consistency of our deployment configuration in other regions and will be taking steps to maintain that consistency.
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 2017-06-29 16:41 UTC, resolved after 0 min, 1 update(s).
- Title
- Increased 503 rates for EU users requesting scoped packages
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/tfjx9s322g92
npm profileRecent npm incidentsAll outages on June 29, 2017npm in June 2017MarkdownJSON