JFrog: JFrog platform services degradation affecting a subset of AWS US East 1 customers due to AWS infrastructure issues

What to do

Check whether you use JFrog Artifactory, Security - Xray, Security - JAS, Security - Curation and 5 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 3d 2h it lasted.
Anything that failed between 2026-05-08 01:21 UTC and 2026-05-11 04:16 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.

identifiedMay 8, 2026, 1:21 AM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringMay 8, 2026, 5:07 AM UTC
Services have auto-recovered basis our high-availability setup and additional configuration enhancements. JFrog engineers remain on standby monitoring the situation closely until AWS fully resolves the underlying Availability Zone impact.
provider
resolvedMay 11, 2026, 4:16 AM UTC
This incident was resolved at May 8 5.30am UTC
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-05-11 04:16 UTC. For JFrog's live state, see https://down.guide/jfrog.

How long did it last?

3d 2h, from 2026-05-08 01:21 UTC to 2026-05-11 04:16 UTC, by the times JFrog posted.

What was affected?

JFrog named Artifactory, Security - Xray, Security - JAS, Security - Curation and 5 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.