- Level
- confirmed
- Worst impact
- Degraded
- Components
- Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines, Pipelines
- Down Index
- 19of 100
What to do
Check whether you use JFrog Pipelines, Pipelines, Pipelines, Pipelines and 7 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 28m it lasted.
Anything that failed between 2024-05-01 17:31 UTC and 2024-05-01 18:59 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 2
- identified
Pipelines users in AWS who rely on the default SaaS buildplane node pools are temporarily unavailable. Custom node pools unaffected.
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-e626b6c9da
Is JFrog still down?
No, this incident was resolved 2024-05-01 18:59 UTC. For JFrog's live state, see https://down.guide/jfrog.
How long did it last?
1h 28m, from 2024-05-01 17:31 UTC to 2024-05-01 18:59 UTC, by the times JFrog posted.
What was affected?
JFrog named Pipelines, Pipelines, Pipelines, Pipelines and 7 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.