JFrog change history

JFrog reported a major Xray service disruption in Azure US East affecting approximately 119 customers, starting 2026-10-08 11:13 UTC and resolved 2026-10-08 13:13 UTC (2 h 0 min). Unexpected issues during emergency database maintenance caused the disruption; JFrog completed database recovery and fully restored services.

JFrog reported a major incident affecting Artifactory in Azure EU West (Netherlands), with some customers potentially experiencing a brief service interruption. It started and was resolved at 2026-08-04 13:24 UTC, with a computed duration of 0 min; JFrog validated service stability and continued monitoring.

A critical JFrog Cloud Platform outage affected a subset of customers using Artifactory and Security - Xray in Azure US West (California), from 2026-07-23 15:04 UTC to 2026-07-23 20:32 UTC, lasting 5 h 27 min. JFrog reported several Azure backend service outages, implemented a fix, and marked the incident resolved.

JFrog reported a critical potential Xray disruption across all regions, with a subset of customers potentially experiencing authentication errors or failures accessing Xray and performing related operations. It started at 2026-07-12 10:45 UTC and was resolved at 2026-07-12 12:45 UTC, lasting 1 h 59 min; no cause or specific fix was stated.

JFrog reported a critical Cloud Platform outage affecting a subset of customers in AWS US East, citing an infrastructure issue. It started at 2026-05-21 06:04 UTC and was resolved at 2026-05-21 06:35 UTC, lasting 31 min; JFrog confirmed all regional services were fully operational and engineers continued monitoring.

JFrog reported a major Artifactory outage affecting a subset of AWS customers in US - West2 (Oregon), attributed to AWS infrastructure issues. It started at 2026-04-22 17:03 UTC and was resolved at 2026-04-22 17:59 UTC, lasting 56 min; JFrog reported implementing a fix at 17:30 UTC.

JFrog reported a major partial outage affecting Azure US West customers, including Artifactory, Distribution, Pipelines, security services, Webhook and Web UI, caused by Azure infrastructure compute issues. It started at 2026-02-07 08:33 UTC and lasted 6 h 52 min; JFrog reported full restoration at 2026-02-07 15:26 UTC after the upstream outage was resolved.

JFrog Connect had a major partial disruption causing some devices to appear offline or disconnected in the dashboard, starting 2025-12-22 08:51 UTC and lasting 47 h 52 min. It was resolved at 2025-12-24 08:44 UTC after engineers applied a fix and verified all devices were reporting status accurately.

JFrog reported a critical Artifactory outage across AWS regions US - East1 (N. Virginia), US - EAST2 (Ohio), US - West1 (California), and US - West2 (Oregon). It lasted 3 h 15 min, from 2025-10-20 07:42 UTC to 2025-10-20 10:57 UTC. JFrog attributed the disruption to AWS; all services were restored.

A major JFrog Cloud Platform outage affected a subset of customers in Azure US East (Virginia), disrupting Artifactory, Distribution, security services and Web UI. It started at 2025-10-10 17:26 UTC and was resolved at 2025-10-10 18:19 UTC, lasting 53 min. JFrog reported recovery by 17:50 UTC and engaged Azure engineering for deeper analysis.

JFrog reported a major Xray outage affecting some customers in US - East (Virginia) on Azure, starting 2025-09-07 12:42 UTC and resolved at 2025-09-07 13:39 UTC (56 min). JFrog attributed the outage to database maintenance, worked with Azure, and reported implementing a fix at 13:04 UTC.

JFrog reported a major outage affecting a subset of AWS US West2 customers, who lost platform connectivity due to an unplanned infrastructure anomaly affecting an internal network. The incident ran from 2025-05-30 19:06 UTC to 2025-05-30 19:39 UTC (32 min); JFrog confirmed all services were back online and fully operational.

JFrog reported a critical UI-login outage for some customers in APAC - SouthEast1 (Singapore) - AWS, Europe - West2 (London) - GCP, and US - West (California) - Azure. It started 2025-03-05 13:49 UTC and was resolved at 2025-03-05 14:42 UTC (52 min); JFrog reported implementing a fix.

JFrog reported major intermittent service disruptions affecting a subset of customers in AWS US West 2 (Oregon), starting 2025-01-13 18:34 UTC and resolved 2025-01-13 20:15 UTC, lasting 1 h 40 min. Affected components included Artifactory, Distribution, Pipelines, security services, Webhook and Web UI; JFrog reported implementing a fix at 19:52 UTC.

JFrog reported a critical platform services outage affecting a subset of customers in Azure US East (Virginia), attributed to infrastructure issues. It started at 2024-12-31 02:41 UTC and lasted 5 h 22 min, affecting Artifactory, Distribution, Pipelines, Security services, Webhook and Web UI. A fix was implemented; the incident was resolved at 2024-12-31 08:03 UTC.

JFrog reported a critical platform services outage due to AWS infrastructure issues, affecting Artifactory, Distribution, Pipelines, security services, Webhook and Web UI in a subset of AWS regions. The outage started at 2024-12-22 13:08 UTC and was resolved at 2024-12-22 14:38 UTC.

JFrog reported a major Xray services outage affecting a subset of customers in Azure EU West (Netherlands), starting 2024-12-20 03:24 UTC and resolved at 2024-12-20 03:51 UTC after 27 min. A fix was implemented by 2024-12-20 03:38 UTC; no cause was stated.

JFrog Xray experienced a major intermittent outage affecting a subset of customers in AWS US East1 (N. Virginia) and Europe - Central1 (Frankfurt). It started at 2024-07-03 12:25 UTC and was resolved at 2024-07-03 13:33 UTC, lasting 1 h 8 min; JFrog reported implementing a fix.

JFrog reported a major outage affecting some customers on AWS US East, with Artifactory, Distribution, Mission Control, Pipelines and Xray listed as affected. It started at 2024-03-28 16:38 UTC and was resolved at 2024-03-28 21:54 UTC, lasting 5 h 16 min; JFrog reported implementing a fix and confirmed all services operational.

JFrog reported a major Cloud Platform UI outage affecting some customers, with Artifactory in US - East1 (N. Virginia) - AWS listed as affected. It started at 2024-03-27 14:41 UTC and resolved at 2024-03-27 16:43 UTC, lasting 2 h 1 min. JFrog said it identified and resolved a frontend application limitation.