Is JFrog down?
Vendor reports no incidentWhat JFrog reports
JFrog reports no incident on its status page.
As of the last successful poll, 2026-10-23 19:47 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Awaiting datachecked 4 minutes ago
Our checks of JFrog pass from 9 of the 10 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.
As of Oct 23, 2026, 7:47 PM UTC, RealUptime's checks of JFrog passed in all 9 regions that returned a reading. RealUptime could not obtain a reading from South America, which is a fact about our own check there and is not evidence about JFrog.
JFrog reports: All systems operational (“All Systems Operational”)
JFrog's own component breakdown, as they publish it
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- ArtifactoryOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - XrayOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
- Security - JASOperational
These are JFrog's components, named and scored by JFrog. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is JFrog's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
JFrog response time, by region
Check your own site while you wait on JFrog
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not JFrog. It cannot diagnose JFrog's own systems.
What we measured, function by function
JFrog answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Awaiting data
Email me when JFrog reports an incident on its status page, and again when it reports it resolved.
Get an email when JFrog reports an incident
Email me when JFrog reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 693msstatus code: 200checked: Oct 23, 2026, 7:45 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach JFrog normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1113msstatus code: 200checked: Oct 23, 2026, 7:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach JFrog normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 402msstatus code: 200checked: Oct 23, 2026, 7:43 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach JFrog normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 599msstatus code: 200checked: Oct 23, 2026, 7:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach JFrog normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaAwaiting datalatency: 11392msstatus code: nonecheck reading: nonechecked: Oct 23, 2026, 7:45 PM UTC0 people in the last 5 minutesNot enough reports to sayJFrog refused our South America probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from South America to say anything on their own.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 874msstatus code: 200checked: Oct 23, 2026, 7:42 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach JFrog normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 701msstatus code: 200checked: Oct 23, 2026, 7:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach JFrog normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1624msstatus code: 200checked: Oct 23, 2026, 7:45 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach JFrog normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 1620msstatus code: 200checked: Oct 23, 2026, 7:45 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach JFrog normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 1786msstatus code: 200checked: Oct 23, 2026, 7:43 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach JFrog normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using JFrog, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for JFrog yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring JFrog since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for JFrog covering any window you pick, with our check readings and JFrog's own claim at the time, side by side.
Full check history for JFrog: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/jfrog)<a href="https://realuptime.io/outages/jfrog"><img src="https://realuptime.io/outages/jfrog/badge.svg?days=30" alt="JFrog uptime by RealUptime's checks" height="20"></a>The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
To cite this page: RealUptime, "Is JFrog down?", https://realuptime.io/outages/jfrog. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means the service's own health route reported that it is up. It does not show that pages, sign-in or the features people use work; a health route can stay green while they fail.
Host checked: releases.jfrog.io