Skip to service list
IU

Is JFrog down?

JFrog status · Developer Tools · checked (6s ago)

Also searched as Artifactory, JFrog Artifactory, JFrog Cloud.

Operational

No — JFrog is not down. All JFrog systems are reported operational.

According to JFrog's official status page, JFrog was reporting “Service Under Maintenance” when isuptime last checked at . Over the last 30 days, JFrog's feed reported no outage in 100.00% of our checks.

No outage reported (30d)
100.00%
Share of our checks where JFrog's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
560 ms
How long the last status check took
Reported by
Operational
Service Under Maintenance

Is JFrog down for you right now?

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.

What JFrog is

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.

What JFrog's status feed covers

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.

JFrog uptime, last 30 days

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.

2026-10-0616 of 30 days recordedToday
  • No outage reported (99%+)
  • 95–99%
  • 80–95%
  • Under 80%
  • No data

Other services reporting problems right now

10 other services isuptime tracks were also reporting a problem as of the same check, 6s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.

2 more services are reporting problems — see all →

JFrog response time trend

Each point is one check of JFrog's status endpoint.

Which JFrog features are affected?

JFrog outage history

JFrog has published 23 incidents in the last 12 months, the 20 most recent shown here. Only what JFrog posted itself — not every problem users hit.

JFrog status — frequently asked

Is JFrog down right now?
No — JFrog is not down. All JFrog systems are reported operational. Checked (6s ago).
What is JFrog's status right now?
JFrog is reporting “Service Under Maintenance” on its official status page — Operational — as of . That status feed answered our last check in 560 ms. isuptime reads this from JFrog's own published feed and does not test JFrog independently.
When did JFrog last go down?
The most recent incident JFrog published was “JFrog Cloud Platform - OIDC Authentication Issues”, opened Oct 29, 11:00 AM UTC (5d ago) and marked resolved Oct 29, 02:04 PM UTC. That is the latest entry in JFrog's own incident feed, not every problem users experienced.
What is JFrog's uptime?
isuptime does not measure JFrog's uptime directly — it reads JFrog's own published status feed. Over the last 30 days, JFrog's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is JFrog down for everyone?
JFrog reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.

JFrog says operational but it is not working for me

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.

Open JFrog's official status page

Other Developer Tools services

← See live status for all 102 services