rewindex

CompaniesnpmIncidents

npm: 503s on packages

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.npmjs.org (opens in new tab)

Timeline of updates

  1. resolved

    Between 11:10 UTC until 12:30 UTC today we saw an elevated rate of 503 on requests for packages and package data. It should now be resolved.

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-09-25 13:37 UTC, resolved after 0 min, 1 update(s).

Title
503s on packages
Vendor
npm
Date
URL
https://rewindex.com/company/npm/incidents/zm23dpx9gy8t

npm profileRecent npm incidentsAll outages on September 25, 2017npm in September 2017MarkdownJSON