npm: public-skimdb is offline while we investigate a configuration error
Timeline of updates
- resolved
skimdb.npmjs.com is back in service. The sequence number advertised by couchdb has changed. Your follow scripts might need to be updated.
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 2016-08-24 20:22 UTC, resolved after 3.2 h, 1 update(s).
- Title
- public-skimdb is offline while we investigate a configuration error
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/jnc8337678r6
npm profileRecent npm incidentsAll outages on August 24, 2016npm in August 2016MarkdownJSON