# JFrog in February 2022: incidents, uptime and changes

> JFrog in February 2022: 1 incident on its status page (1 major or critical), 98.38% free of major or critical incidents (vendor-reported). From Rewindex’s archive of JFrog’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/jfrog/2022/02
Last updated: 2022-03-01T00:00:00Z

- Incidents posted: 1 (major/critical: 1) · Maintenance: 3
- By vendor impact label: major 1
- Uptime (vendor-reported): 98.38% free of major/critical incidents, 98.38% free of any incident; outage time 10 h 53 min, incident time 10 h 53 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [January 2022](https://rewindex.com/company/jfrog/2022/01.md) · Next: [March 2022](https://rewindex.com/company/jfrog/2022/03.md) · [All months](https://rewindex.com/company/jfrog/reports.md) · [JFrog](https://rewindex.com/company/jfrog.md)

_Uptime: 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._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Unplanned\] JFrog Cloud Platform maintenance](https://rewindex.com/company/jfrog/incidents/1f858cn1dnrt.md) | major | 2022-02-04 20:26 UTC | 2022-02-05 07:19 UTC | 11 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Unplanned\] JFrog Cloud Platform maintenance](https://rewindex.com/company/jfrog/incidents/1f858cn1dnrt.md) | major | 2022-02-04 20:26 UTC | 2022-02-05 07:19 UTC | 11 h | resolved |

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] \[Scheduled\] JFrog Cloud Platform Azure DB Maintenance](https://rewindex.com/company/jfrog/incidents/vss4ytpxddcp.md) | maintenance | 2022-02-05 07:35 UTC | 2022-02-05 22:35 UTC | 15 h | resolved |
| [\[Scheduled\] JFrog Cloud Platform Database Maintenance - GCP US West 1](https://rewindex.com/company/jfrog/incidents/32jlpv33hj4p.md) | maintenance | 2022-02-20 11:25 UTC | 2022-02-20 12:25 UTC | 1.0 h | resolved |
| [\[Scheduled\] JFrog Cloud Platform Database Maintenance on GCP regions](https://rewindex.com/company/jfrog/incidents/gtbs3cgfdts2.md) | maintenance | 2022-02-27 09:45 UTC | 2022-02-27 10:45 UTC | 1.0 h | resolved |

## Cite this

JFrog posted 1 status incident in February 2022 (1 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/jfrog/2022/02
- Citation: JFrog, “JFrog in February 2022” (2022-02-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/jfrog/2022/02 (CC BY 4.0).
- Markdown link: `[JFrog: JFrog in February 2022 (2022-02-01)](https://rewindex.com/company/jfrog/2022/02)`


---
Canonical: https://rewindex.com/company/jfrog/2022/02 · Markdown: https://rewindex.com/company/jfrog/2022/02.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T11:04:43.979Z