rewindex

CompaniesnpmIncidents

npm: Publishes over HTTP appear to succeed but are ignored

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

Timeline of updates

  1. resolved

    The fix is good! Publishes are now accepted over HTTP, but you aren't doing that, are you?

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 2018-05-30 20:34 UTC, resolved after 3.4 h, 1 update(s).

Title
Publishes over HTTP appear to succeed but are ignored
Vendor
npm
Date
URL
https://rewindex.com/company/npm/incidents/mnm1x5yrp9p1

npm profileRecent npm incidentsAll outages on May 30, 2018npm in May 2018MarkdownJSON