rewindex

CompaniesnpmMonthly reportsJune 2018

npm in June 2018: incidents, uptime and changes

10incidents posted
1labelled major or critical
99.51%free of major/critical
90.85%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 3 h 28 min, incident time 2.7 days. 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: Major 1 · Minor 4 · No impact listed 5

Major and critical incidents 1

IncidentImpactStartedDurationStatusDay
slow reponses from replicate.npmjs.comMajor3.5 hresolved06-22

Other incidents 9

IncidentImpactStartedDurationStatusDay
Download counts not being properly updatedNo impact listed38 dresolved06-04
Intermittent 429 status code returnsMinor22 hresolved06-04
Intermittent 503's status returnsNo impact listed4.7 hresolved06-06
Intermittent 503s and 504sNo impact listed2.5 hresolved06-08
We are currently investigating an uptick of 503 and 504 return codesNo impact listed3.1 hresolved06-13
Errors with signups, contact forms, and new publishesNo impact listed7.3 hresolved06-21
404s on certain registry readsMinor10 hresolved06-27
Intermittent 500 errors when installing packagesMinor5.1 hresolved06-28
404s on certain registry readsMinor29 hresolved06-28

Cite this

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

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

All npm monthsRecent incidentsMarkdown