CompaniesnpmMonthly reportsJanuary 2017
npm in January 2017: incidents, uptime and changes
4incidents posted
0labelled major or critical
100%free of major/critical
99.86%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 59 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 1 · No impact listed 3
Incidents 4
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| website not responding | Minor | 59 min | resolved | 01-05 | |
| increased origin latency resulting in burst of 503s | No impact listed | 0 min | resolved | 01-13 | |
| Increased 503 rates for users in Los Angeles region | No impact listed | 0 min | resolved | 01-25 | |
| some readmes are unavailable on npmjs.com | No impact listed | 3.7 h | resolved | 01-26 |
Cite this
npm posted 4 status incidents in January 2017 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- npm in January 2017
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/2017/01