rewindex

CompaniesnpmMonthly reportsMarch 2016

npm in March 2016: incidents, uptime and changes

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

Vendor-reported outage time 0 min, incident time 3 h 31 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: Minor 2 · No impact listed 9

Incidents 11

IncidentImpactStartedDurationStatusDay
Increased registry 503 ratesMinor2.3 hresolved03-02
elevated 404 rates for scoped modulesNo impact listed0 minresolved03-09
503s on installsNo impact listed18 minresolved03-10
elevated 503s for json from the SJC PoPNo impact listed52 minresolved03-11
Increased 504 rates for tarballsMinor1.2 hresolved03-17
increase 503 rate from our Australia based tarball serversNo impact listed17 minresolved03-17
Website and private package installation issuesNo impact listed2.1 hresolved03-24
increased publish latencyNo impact listed30 minresolved03-24
Increased 502 rates for publishesNo impact listed47 minresolved03-24
Increased publish error ratesNo impact listed5 minresolved03-25
Partially-failed publications earlier todayNo impact listed4.3 hresolved03-25

Cite this

npm posted 11 status incidents in March 2016 (0 major or critical); 0 price changes and 0 notable page changes observed.

Title
npm in March 2016
Vendor
npm
Date
URL
https://rewindex.com/company/npm/2016/03

All npm monthsRecent incidentsMarkdown