Skip to main content
JFrog

JFrog Cloud Platform outage affecting subset of customers in AWS US East region

Major outage Lasted 31m · started · JFrog's page

Level
confirmed
Worst impact
Major 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 31m it lasted.

    Anything that failed between 2026-05-21 06:04 UTC and 2026-05-21 06:35 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

  1. investigating

    We are currently investigating an infrastructure issue in the AWS US East region that may impact a limited number of customers. Our engineering team is actively working to restore full service.

    provider

  2. resolved

    The issue has been resolved. All services in the AWS US East region are fully operational. JFrog Engineers are continuing to monitor to ensure stability.

    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-a7d190450f

Is JFrog still down?

No, this incident was resolved 2026-05-21 06:35 UTC. For JFrog's live state, see https://down.guide/jfrog.

How long did it last?

31m, from 2026-05-21 06:04 UTC to 2026-05-21 06:35 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.