- Level
- confirmed
- Worst impact
- Degraded
- Components
- Security - Xray, Security - Xray, Security - JAS, Security - JAS, Security - JAS
What to do
Check whether you use JFrog Security - Xray, Security - Xray, Security - JAS, Security - JAS and 1 more. 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 1h 34m it lasted.
Anything that failed between 2024-10-31 13:17 UTC and 2024-10-31 14:51 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 3
- investigating
We are investigating cases of degraded performance for JFrog Cloud Platform customers. We will provide more details within the next hour.
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-7e6f91ed84
Is JFrog still down?
No, this incident was resolved 2024-10-31 14:51 UTC. For JFrog's live state, see https://down.guide/jfrog.
How long did it last?
1h 34m, from 2024-10-31 13:17 UTC to 2024-10-31 14:51 UTC, by the times JFrog posted.
What was affected?
JFrog named Security - Xray, Security - Xray, Security - JAS, Security - JAS and 1 more.
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.