CompaniesJFrogMonthly reportsFebruary 2017
JFrog in February 2017: incidents, uptime and changes
3incidents posted
1labelled major or critical
99.53%free of major/critical
98.75%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 3 h 8 min, incident time 8 h 24 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: Major 1 · Minor 1 · No impact listed 1
Major and critical incidents 1
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Connectivity issue reported by Amazon in their AWS infrastructure in California | Major | 3.1 h | resolved | 02-10 |
Other incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Unscheduled restart | No impact listed | 0 min | resolved | 02-22 | |
| S3 outage reported by AWS in USE | Minor | 5.3 h | resolved | 02-28 |
Cite this
JFrog posted 3 status incidents in February 2017 (1 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- JFrog in February 2017
- Vendor
- JFrog
- Date
- URL
- https://rewindex.com/company/jfrog/2017/02