npm: Elevated 503s for users near Washington, D.C.
Timeline of updates
- resolved
From 0040 to 0110 PT (0840 to 0911 UTC) our CDN Point of Presence near Washington D.C. experienced networking issues that led to the registry serving 503s. Up to 1.5% of registry responses were 503 for the first 10 minutes, then a much smaller percentage (~0.1%) until the problem was entirely resolved. Only users physically close to Washington D.C. were affected.
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 2014-11-19 09:19 UTC, resolved after 0 min, 1 update(s).
- Title
- Elevated 503s for users near Washington, D.C.
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/bn3hx5z1vq3t
npm profileRecent npm incidentsAll outages on November 19, 2014npm in November 2014MarkdownJSON