rewindex

CompaniesnpmMonthly reportsMarch 2017

npm in March 2017: incidents, uptime and changes

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

Incidents 5

IncidentImpactStartedDurationStatusDay
increased rate of 503s.No impact listed0 minresolved03-15
Delayed Package PublishesNo impact listed1.2 hresolved03-17
replication lag on publicationsNo impact listed7.0 hresolved03-24
increased rate of 503s in euNo impact listed1.0 hresolved03-28
forced unpublishes currently failingNo impact listed6.6 hresolved03-29

Cite this

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

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

All npm monthsRecent incidentsMarkdown