# JFrog in January 2026: incidents, uptime and changes

> JFrog in January 2026: 0 incidents on its status page (0 major or critical), 100% free of major or critical incidents (vendor-reported), 1 CVE. From Rewindex’s archive of JFrog’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/jfrog/2026/01
Last updated: 2026-10-07T11:10:00Z

- Incidents posted: 0 (major/critical: 0) · Maintenance: 5
- By vendor impact label: none
- Uptime (vendor-reported): 100% free of major/critical incidents, 100% free of any incident; outage time 0 min, incident time 0 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 1
- Previous month: [December 2025](https://rewindex.com/company/jfrog/2025/12.md) · Next: [February 2026](https://rewindex.com/company/jfrog/2026/02.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._

## All incidents

_No incidents posted this month._

## CVEs published

- [CVE-2025-14830](https://rewindex.com/cve/CVE-2025-14830.md) JFrog Artifactory Cross-Site Scripting (CVSS 4.9), published 2026-01-04

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] JFrog Cloud Platform Database Maintenance in GCP London, Mumbai and Hong Kong](https://rewindex.com/company/jfrog/incidents/k6546m44nb3p.md) | maintenance | 2026-01-04 07:00 UTC | 2026-01-04 09:00 UTC | 2.0 h | resolved |
| [\[Scheduled\] JFrog Cloud Platform Database Maintenance in GCP Netherlands, Tel Aviv and Iowa](https://rewindex.com/company/jfrog/incidents/1slbwdsjz5nb.md) | maintenance | 2026-01-04 08:00 UTC | 2026-01-04 10:00 UTC | 2.0 h | resolved |
| [\[Scheduled\] JFrog Cloud Platform Database Maintenance in GCP USA](https://rewindex.com/company/jfrog/incidents/q5p9slbl5wty.md) | maintenance | 2026-01-04 09:01 UTC | 2026-01-04 10:01 UTC | 1.0 h | resolved |
| [\[Scheduled\] Emergency Database Maintenance](https://rewindex.com/company/jfrog/incidents/6rn197rygn1p.md) | maintenance | 2026-01-11 08:00 UTC | 2026-01-11 10:00 UTC | 2.0 h | resolved |
| [\[Scheduled\] Planned Cloud Maintenance on GCP APAC - HongKong , Mumbai Regions](https://rewindex.com/company/jfrog/incidents/5gkh50080vv0.md) | maintenance | 2026-01-23 17:50 UTC | 2026-01-24 01:50 UTC | 8.0 h | resolved |

## Cite this

JFrog posted 0 status incidents in January 2026 (0 major or critical); 0 price changes and 0 notable page changes observed.

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


---
Canonical: https://rewindex.com/company/jfrog/2026/01 · Markdown: https://rewindex.com/company/jfrog/2026/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T17:38:03.429Z