- Level
- confirmed
- Worst impact
- Partial outage
- Components
- JFrog Connect
- Down Index
- 33of 100
What to do
Check whether you use JFrog JFrog Connect. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 23h it lasted.
Anything that failed between 2025-12-22 08:51 UTC and 2025-12-24 08:44 UTC may need a replay.Subscribe to JFrog's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=jfrog works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from JFrog 2
- investigating
JFrog Engineers are currently investigating an issue causing some devices to appear as offline or disconnected in the dashboard. Our engineering team is actively working on the resolution. Service functionality remains a priority and we will provide a follow-up as soon as we have more information. We apologize for the interruption.
provider
- resolved
JFrog engineers have applied the fix and all devices are verified to be reporting status accurately.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e262fe6a0f
Is JFrog still down?
No, this incident was resolved 2025-12-24 08:44 UTC. For JFrog's live state, see https://down.guide/jfrog.
How long did it last?
1d 23h, from 2025-12-22 08:51 UTC to 2025-12-24 08:44 UTC, by the times JFrog posted.
What was affected?
JFrog named JFrog Connect.
What caused it?
JFrog hasn't published a root cause. If it does, it shows here.
Where does this come from?
JFrog's official status page, https://status.jfrog.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.