- Level
- confirmed
- Worst impact
- Operational
- Components
- Artifactory, Distribution, Pipelines
- Regions
- us
What to do
Check whether you use JFrog Artifactory, Distribution, Pipelines 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 3h 48m it lasted.
Anything that failed between 2024-03-27 12:46 UTC and 2024-03-27 16:34 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
- investigating
We are investigating an availability issue that is impacting some JFrog Cloud Platform customers on Azure US East. We will provide more details within the next hour.
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
- resolved
A fix was applied a while ago, all the services were observed to be stable and fully operational. Incident stands 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-19cd0a30cc
Is JFrog still down?
No, this incident was resolved 2024-03-27 16:34 UTC. For JFrog's live state, see https://down.guide/providers/jfrog.
How long did it last?
3h 48m, from 2024-03-27 12:46 UTC to 2024-03-27 16:34 UTC, by the times JFrog posted.
What was affected?
JFrog named Artifactory, Distribution, Pipelines 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.