Live  /  Providers  /  JFrog Cloud

JFrog Cloud

jfrog.ioNo open incidents

Independent assessment — SquidGrid is not affiliated with JFrog Cloud. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks JFrog Cloud’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what JFrog Cloud is reporting

Current & recent incidents

Resolved

JFrog Cloud Platform - OIDC Authentication Issues

Minor impact · 2026-10-29 14:17 UTC · source

Resolved

JFrog Cloud Platform - Multiple Service Disruptions in GCP Europe West

Critical impact · 2026-10-20 12:10 UTC · source

Resolved

JFrog Cloud Platform - Xray Service Disruption in Azure US East

Major impact · 2026-10-08 13:44 UTC · source

Resolved

Potential slowdown on Maven remotes in AWS Europe Central

Minor impact · 2026-09-30 21:39 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 6 incidents from JFrog Cloud’s own status page since 2026-09-30.

Recent incidents in the archive

Computed by SquidGrid from the incidents JFrog Cloud published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what JFrog Cloud has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

JFrog Cloud runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of JFrog Cloud is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with JFrog Cloud.