rewindex

CompaniesnpmMonthly reportsJune 2017

npm in June 2017: incidents, uptime and changes

4incidents 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 4

Incidents 4

IncidentImpactStartedDurationStatusDay
Increased 503 rates for public packagesNo impact listed5 minresolved06-09
Experiencing problems with scoped package downloadsNo impact listed6 minresolved06-13
Increased error rates due to a CDN provider outageNo impact listed0 minresolved06-28
Increased 503 rates for EU users requesting scoped packagesNo impact listed0 minresolved06-29

Cite this

npm posted 4 status incidents in June 2017 (0 major or critical); 0 price changes and 0 notable page changes observed.

Title
npm in June 2017
Vendor
npm
Date
URL
https://rewindex.com/company/npm/2017/06

All npm monthsRecent incidentsMarkdown