rewindex

CompaniesnpmIncidents

npm: www search 503

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

Timeline of updates

  1. resolved

    we found some invalid search queries causing increased load on our search cluster. we are adding additional filtering and should be out of the woods.

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-02-16 14:35 UTC, resolved after 1.4 h, 1 update(s).

Title
www search 503
Vendor
npm
Date
URL
https://rewindex.com/company/npm/incidents/t9bq2qr9tnkx

npm profileRecent npm incidentsAll outages on February 16, 2017npm in February 2017MarkdownJSON