- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
What to do
Check whether you use JFrog in us. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 9m it lasted.
Anything that failed between 2024-07-03 12:25 UTC and 2024-07-03 13:33 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 5
- investigating
We are currently investigating this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
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-6f530f4393
Is JFrog still down?
No, this incident was resolved 2024-07-03 13:33 UTC. For JFrog's live state, see https://down.guide/providers/jfrog.
How long did it last?
1h 9m, from 2024-07-03 12:25 UTC to 2024-07-03 13:33 UTC, by the times JFrog posted.
What was affected?
JFrog named in us.
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.