rewindex

CompaniesnpmMonthly reportsFebruary 2018

npm in February 2018: incidents, uptime and changes

6incidents posted
0labelled major or critical
100%free of major/critical
100%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 0 min, incident time 0 min. Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours. Last 90 days.

By vendor label: No impact listed 6

Incidents 6

IncidentImpactStartedDurationStatusDay
`package`, `delete`, and `dumbledore` packages unavailableNo impact listed3.4 hresolved02-01
415 errors when publishing some packagesNo impact listed51 minresolved02-06
404s for teamsNo impact listed1.8 hresolved02-07
publication tarball size temporarily limited to 50MBNo impact listed18 hresolved02-07
some publishes appear to succeed but don'tNo impact listed27 hresolved02-09
Increased rate of timeouts for authenticated actions.No impact listed57 minresolved02-20

Cite this

npm posted 6 status incidents in February 2018 (0 major or critical); 0 price changes and 0 notable page changes observed.

Title
npm in February 2018
Vendor
npm
Date
URL
https://rewindex.com/company/npm/2018/02

All npm monthsRecent incidentsMarkdown