← Back to JFrog's check readings
We started checking JFrog on August 22, 2026, which is 64 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when JFrog reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what JFrog's own status page declared. Below it, any public chatter we saw about JFrog and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what JFrog's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about JFrog in the last 24 hours, which is not evidence that nothing is wrong.
JFrog's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is JFrog's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention JFrog next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
JFrog's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
JFrog Cloud Platform - Multiple Service Disruptions in GCP Europe WestMajor outage
Oct 20, 2026, 6:04 AM UTC to Oct 20, 2026, 12:10 PM UTC (6h 6m)resolved
their latest update (Oct 20, 2026, 12:10 PM UTC): All affected services in our GCP Europe West region have been fully restored, and all customers are operating normally.
We have validated the recovery and confirmed that service health and availability have returned to normal, with no further issues identified.
We will continue …
JFrog Cloud Platform - Multiple Service Disruptions in Azure Southeast AsiaMajor outage
Oct 18, 2026, 7:08 AM UTC to Oct 18, 2026, 9:40 AM UTC (2h 31m)resolved
their latest update (Oct 18, 2026, 9:40 AM UTC): The issue affecting Artifactory and Xray services in our Azure Southeast Asia region has been resolved.
The affected services have been restored, and service health has returned to normal following the recovery of the underlying database infrastructure.
JFrog Cloud Platform outage affecting subset of customers in AWS US East regionAll systems operational
Oct 9, 2026, 10:50 PM UTC to Oct 9, 2026, 11:20 PM UTC (29 min)resolved
their latest update (Oct 9, 2026, 11:20 PM UTC): This incident has been resolved.
JFrog Cloud Platform - Xray Service Disruption in Azure US EastPartial outage
Oct 8, 2026, 11:13 AM UTC to Oct 8, 2026, 1:13 PM UTC (2h)resolved
their latest update (Oct 8, 2026, 1:13 PM UTC): The database recovery has been completed successfully, and Xray services in the Azure US East region have been fully restored.
All affected services are operating normally, and the issue is now resolved.
Potential slowdown on Maven remotes in AWS Europe CentralMinor incident
Sep 30, 2026, 7:07 PM UTC to Sep 30, 2026, 9:39 PM UTC (2h 31m)resolved
their latest update (Sep 30, 2026, 9:39 PM UTC): This incident has been resolved.
JFrog Cloud Platform degraded performance for GCP regionsAll systems operational
Sep 29, 2026, 8:00 AM UTC to Sep 29, 2026, 8:00 AM UTC (0 min)resolved
their latest update (Sep 29, 2026, 8:00 AM UTC): We identified an issue affecting Artifactory upload and download functionality for some customers hosted in the Google Cloud Platform (GCP) US Central, US West, and Europe West regions
The investigation indicates the issue originated with our cloud provider, Google Cloud.
Servic…
Potential UI bug for a subset of customers on JFrog Cloud PlatformAll systems operational
Sep 24, 2026, 5:30 AM UTC to Sep 24, 2026, 5:30 AM UTC (0 min)resolved
their latest update (Sep 24, 2026, 5:30 AM UTC): A subset of customers may have faced UI errors in the Packages page, the problem was detected and mitigated in realtime.
JFrog Cloud Platform degraded performance for Azure US West RegionMinor incident
Aug 5, 2026, 1:14 PM UTC to Aug 5, 2026, 1:21 PM UTC (7 min)resolved
their latest update (Aug 5, 2026, 1:21 PM UTC): The issue has been resolved. The service disruption lasted approximately nine minutes, during which some Artifactory services were temporarily unavailable.
All affected services have fully recovered and are operating normally. The environment is healthy, and our monitoring confi…
JFrog Cloud Platform performance degradation for Azure EU West RegionPartial outage
Aug 4, 2026, 1:24 PM UTC to Aug 4, 2026, 1:24 PM UTC (0 min)resolved
their latest update (Aug 4, 2026, 1:24 PM UTC): The issue affecting some JFrog Cloud Platform customers in the Azure EU West region has been resolved.
During the incident, some customers may have experienced a brief service interruption.
Our team investigated the issue, validated service stability and continues to monitor the…
JFrog Cloud Platform outage affecting subset of customers in Azure US West regionMajor outage
Jul 23, 2026, 3:04 PM UTC to Jul 23, 2026, 8:32 PM UTC (5h 27m)resolved
their latest update (Jul 23, 2026, 8:32 PM UTC): This incident has been resolved.
Showing the 10 most recent of 57 incidents JFrog has declared in the history we hold.
These entries are JFrog's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
JFrog's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.