# JFrog in February 2017: incidents, uptime and changes

> JFrog in February 2017: 3 incidents on its status page (1 major or critical), 99.53% 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/2017/02
Last updated: 2017-03-01T00:00:00Z

- Incidents posted: 3 (major/critical: 1) · Maintenance: 0
- By vendor impact label: major 1, minor 1, none 1
- Uptime (vendor-reported): 99.53% free of major/critical incidents, 98.75% free of any incident; outage time 3 h 8 min, incident time 8 h 24 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [January 2017](https://rewindex.com/company/jfrog/2017/01.md) · Next: [March 2017](https://rewindex.com/company/jfrog/2017/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 |
| --- | --- | --- | --- | --- | --- |
| [Connectivity issue reported by Amazon in their AWS infrastructure in California](https://rewindex.com/company/jfrog/incidents/xy7rh7hdyv1f.md) | major | 2017-02-10 01:20 UTC | 2017-02-10 04:28 UTC | 3.1 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Connectivity issue reported by Amazon in their AWS infrastructure in California](https://rewindex.com/company/jfrog/incidents/xy7rh7hdyv1f.md) | major | 2017-02-10 01:20 UTC | 2017-02-10 04:28 UTC | 3.1 h | resolved |
| [Unscheduled restart](https://rewindex.com/company/jfrog/incidents/4n5pxyr8t6yq.md) | none | 2017-02-22 21:22 UTC | 2017-02-22 21:22 UTC | 0 min | resolved |
| [S3 outage reported by AWS in USE](https://rewindex.com/company/jfrog/incidents/2rr4qjqbdntt.md) | minor | 2017-02-28 17:40 UTC | 2017-02-28 22:56 UTC | 5.3 h | resolved |

## Cite this

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

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


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