Skip to main content
JFrog

JFrog Cloud Platform Service Disruption in GCP Central Region

Degraded Lasted 1h 25m · started · JFrog's page

Level
confirmed
Worst impact
Degraded
Components
Artifactory, Security - Xray, Security - JAS, Security - Curation, Security - Catalog, Security - Runtime, Distribution, Pipelines, Web UI, Webhook

What to do

  • Check whether you use JFrog Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 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 25m it lasted.

    Anything that failed between 2025-08-06 03:52 UTC and 2025-08-06 05:17 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 3

  1. investigating

    We are currently investigating this issue.

    provider

  2. monitoring

    We are investigating a brief service disruption in the GCP Central region caused by a cloud provider network issue All services are up & running stable now & we are continuing to monitor the service health

    provider

  3. resolved

    Cloud Provider has confirmed that the issue has been resolved. No further service disruptions were observed since the last update.

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

Is JFrog still down?

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

How long did it last?

1h 25m, from 2025-08-06 03:52 UTC to 2025-08-06 05:17 UTC, by the times JFrog posted.

What was affected?

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