rewindex

CompaniesJFrogMonthly reportsApril 2019

JFrog in April 2019: incidents, uptime and changes

5incidents posted
5labelled major or critical
94.24%free of major/critical
94.24%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 41 h 27 min, incident time 41 h 27 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 5

Major and critical incidents 5

IncidentImpactStartedDurationStatusDay
Partial outage in Artifactory SaaS in AWS OregonMajor2.4 hresolved04-16
Artifactory Pro Customers receiving 500 errors in Azure US EastMajor4.2 hresolved04-17
Degraded performance in Artifactory SaaS - AWS US West 2 OregonMajor7.0 hresolved04-23
Partial outage in Artifactory SaaS in AWS US East 1 (N. Virginia)Major53 minresolved04-29
AWS US East1 region Artifactory partial outageMajor27 hresolved04-29

Cite this

JFrog posted 5 status incidents in April 2019 (5 major or critical); 0 price changes and 0 notable page changes observed.

Title
JFrog in April 2019
Vendor
JFrog
Date
URL
https://rewindex.com/company/jfrog/2019/04

All JFrog monthsRecent incidentsMarkdown