rewindex

CompaniesJFrogMonthly reportsJune 2020

JFrog in June 2020: incidents, uptime and changes

8incidents posted
6labelled major or critical
87.10%free of major/critical
86.49%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 3.9 days, incident time 4.1 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: Critical 1 · Major 5 · Minor 1 · No impact listed 1

Major and critical incidents 6

IncidentImpactStartedDurationStatusDay
AWS US West 2 region 503 errorsCritical29 hresolved06-04
Pipeline 503 errors in AWS USE1 RegionMajor9.4 hresolved06-10
Outage on service Pipelines in AWS EU Central 1Major33 hresolved06-11
Pipeline 503 errors in AWS USE1 RegionMajor15 hresolved06-12
AWS US West 2 region outageMajor13 hresolved06-18
AWS US West 2 Region Partial OutageMajor8.3 hresolved06-24

Other incidents 2

IncidentImpactStartedDurationStatusDay
503 errors in AWS USE1 regionNo impact listed4.8 hresolved06-11
We are experiencing an issue with Google Compute Engine and Cloud Networking in us-east1Minor4.4 hresolved06-29

Cite this

JFrog posted 8 status incidents in June 2020 (6 major or critical); 0 price changes and 0 notable page changes observed.

Title
JFrog in June 2020
Vendor
JFrog
Date
URL
https://rewindex.com/company/jfrog/2020/06

All JFrog monthsRecent incidentsMarkdown