CompaniesnpmMonthly reportsOctober 2017
npm in October 2017: incidents, uptime and changes
3incidents 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 3
Incidents 3
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| increased rate of 503s in European and East Coast POPs | No impact listed | 23 min | resolved | 10-18 | |
| Registry and Website reads | No impact listed | 1.3 h | resolved | 10-22 | |
| 503s on npmjs website and package pages | No impact listed | 29 min | resolved | 10-25 |
Cite this
npm posted 3 status incidents in October 2017 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- npm in October 2017
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/2017/10