Loading status…
JFrog status · Developer Tools · checked (3s ago)
Also searched as Artifactory, JFrog Artifactory, JFrog Cloud.
No — JFrog is not down. All JFrog systems are reported operational.
According to JFrog's official status page, JFrog was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, JFrog's feed reported no outage in 100.00% of our checks.
Everything above is read from JFrog's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported JFrog in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
JFrog runs Artifactory, the binary repository most enterprises put in front of every package manager they use — Maven, npm, Docker, PyPI, Go — along with Xray for scanning and the wider JFrog Platform. When it is unavailable, builds cannot resolve dependencies and deploys cannot pull images.
This is JFrog's cloud status page, and it reports by region and by service edition. Self-hosted Artifactory, which is still how a large share of enterprises run it, is not covered here at all. Remote repositories proxying npm, Docker Hub or Maven Central can also fail because the upstream is down while JFrog itself is healthy.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where JFrog's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days JFrog was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 3s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of JFrog's status endpoint.
JFrog has published 17 incidents in the last 12 months, newest first. Only what JFrog posted itself — not every problem users hit.
resolved · Aug 5, 01:14 PM (45d ago)
resolved · Aug 4, 01:24 PM (46d ago)
resolved · Jul 23, 03:04 PM (58d ago)
resolved · Jul 12, 10:45 AM (69d ago)
resolved · Jun 10, 05:32 AM (102d ago)
resolved · May 21, 06:04 AM (122d ago)
resolved · May 20, 10:35 AM (122d ago)
resolved · May 8, 01:21 AM (135d ago)
resolved · Apr 24, 03:39 PM (148d ago)
resolved · Apr 22, 05:03 PM (150d ago)
resolved · Mar 2, 08:29 AM (201d ago)
resolved · Feb 7, 08:33 AM (224d ago)
resolved · Dec 22, 08:51 AM (271d ago)
resolved · Dec 11, 05:34 PM (282d ago)
resolved · Nov 11, 12:29 AM (313d ago)
resolved · Oct 20, 07:42 AM (334d ago)
resolved · Oct 10, 05:26 PM (344d ago)
A `401` or `403` from Artifactory is usually a token that expired or a permission target that changed, not an outage. If one repository type fails while others work, check whether it is a remote proxy and whether its upstream is up — JFrog will report an error that reads as its own. Storage quota exhaustion on a cloud plan blocks writes while reads continue perfectly.
