Artifactory Service outage affecting multiple customers across several AWS regions

What to do

• Check whether you use JFrog Artifactory, Artifactory, Artifactory, Artifactory. 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 3h 16m it lasted.

  Anything that failed between 2025-10-20 07:42 UTC and 2025-10-20 10:57 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

1. investigatingOct 20, 2025, 7:42 AM UTC

   We are currently investigating this issue.

   provider

2. investigatingOct 20, 2025, 8:01 AM UTC

   Service disruption confirmed to be caused by an issue with the AWS Cloud vendor. JFrog Engg teams are engaged, analyzing the vendor's progress, and monitoring service stability

   provider

3. monitoringOct 20, 2025, 9:45 AM UTC

   AWS are resuming their services and we see a positive impact on JFrog services. SLO is almost 100% and all Artifactory transactions have been resumed. We are still monitoring the systems health. AWS Incident status chronology can be referred here: https://health.aws.amazon.com/health/status

   provider

4. resolvedOct 20, 2025, 10:57 AM UTC

   All services are up and running - see also https://health.aws.amazon.com/health/status

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.