Is JFrog Artifactory down right now?

No. Our checks are finding no problems with JFrog Artifactory right now. That verdict is live, and the banner at the top of this page carries it too. We re-check JFrog Artifactory continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are clone / push failing, downloads failing, upload failing, API errors, can't connect, builds / pipelines stuck, no response / timing out and rate limited. Those are the options the report button offers for JFrog Artifactory, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With JFrog Artifactory specifically, Artifactory has regional instances and repository-specific access controls, so one repository or region may be unreachable while others work, or your credentials may have expired without affecting other users. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For JFrog Artifactory, try downloading a public artifact directly from your Artifactory instance URL using curl or your package manager, and check that your API token is still valid in your Artifactory user settings. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on JFrog Artifactory's side. Specifically: do not retry builds in a loop, as this will queue thousands of failed jobs and make recovery slower once the service returns; instead, pause CI pipelines and wait for the status page to show recovery. Reporting it here helps other people see they are not alone.

Continuously, around the clock. JFrog Artifactory does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe artifactory.io directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what JFrog Artifactory says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.jfrog.io, and it is linked further up this page. That is JFrog Artifactory's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to JFrog Artifactory or artifactory.io. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need JFrog Artifactory's own support, not us.