- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook
- Regions
- us
What to do
Check whether you use JFrog Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more in us. 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 6h 53m it lasted.
Anything that failed between 2026-02-07 08:33 UTC and 2026-02-07 15:26 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 4
- identified
Summary: We are currently experiencing a partial service disruption affecting customers in the Azure US West region. This is due to underlying compute issues at the Microsoft Azure infrastructure layer. Action: JFrog Engineers are actively working to mitigate the impact and recover services.
provider
- identified
Microsoft Azure engineering is actively working on restoring services at the infrastructure layer. JFrog Engg Team is monitoring the progress closely as they address the underlying compute failure. Official Microsoft outage details and status updates can be tracked at: https://app.azure.com/h/JLPW-7W8/86af1b
provider
- identified
JFrog Engg have recovered Artifactory services for all customers in the region Azure US West region. Azure Infrastructure is still not fully stable & Microsoft Team is continuing to work on it.
provider
- resolved
Status: Resolved / Post-Recovery Validation Impact: Services Restored JFrog services are now fully operational following the resolution of a significant upstream infrastructure outage within Azure. Our internal automated monitoring confirms that all our core functionalities have returned to expected performance levels. Recovery & Ongoing Validation While primary connectivity and service layers have been restored, the JFrog engineering team remains in an active monitoring phase. We are currently performing comprehensive validations across all Azure services including storage and compute components. This process ensures that all dependent systems have achieved full synchronization and are performing at optimal capacity. Incident Timeline (UTC) 12:30 UTC: The infrastructure provider confirmed the restoration of facility power and physical network connectivity. Subsequent Window: Azure Cloud services were recovered, enabling the sequential restoration and stabilization of the JFrog service layers. For further technical details regarding the root cause of the underlying infrastructure failure, please refer to the official Azure Status Page - https://azure.status.microsoft/en-us/status
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-ab5b4ac7be
Is JFrog still down?
No, this incident was resolved 2026-02-07 15:26 UTC. For JFrog's live state, see https://down.guide/jfrog.
How long did it last?
6h 53m, from 2026-02-07 08:33 UTC to 2026-02-07 15:26 UTC, by the times JFrog posted.
What was affected?
JFrog named Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more 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.