JFrog: Potential JFrog Xray Service Disruption Across All Regions

What to do

Check whether you use JFrog Security - Xray, Security - Xray, Security - Xray, Security - Xray and 6 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 59m it lasted.
Anything that failed between 2026-07-12 10:45 UTC and 2026-07-12 12:45 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.

investigatingJul 12, 2026, 10:45 AM UTC
We are investigating a potential service disruption affecting JFrog Xray across all regions. A subset of customers may experience authentication errors or failures when accessing Xray and performing Xray-related operations. Our engineering teams are actively working to restore normal service. We will provide another update within the next hour.
provider
resolvedJul 12, 2026, 12:45 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is JFrog still down?

No, this incident was resolved 2026-07-12 12:45 UTC. For JFrog's live state, see https://down.guide/jfrog.

How long did it last?

1h 59m, from 2026-07-12 10:45 UTC to 2026-07-12 12:45 UTC, by the times JFrog posted.

What was affected?

JFrog named Security - Xray, Security - Xray, Security - Xray, Security - Xray and 6 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.