JFrog: JFrog Cloud Platform users might experience broken Set Me Up flow affecting subset of JFrog customers
Affected components: APAC - SouthEast1 (Singapore) - AWS - Web UIWeb UIUS - Central1 (Iowa) - GCP - Web UIWeb UIUS - South Central (Texas) - Azure - Web UIWeb UIEMEA - South Africa (Cape Town) - AWS - Web UIWeb UIEurope - West4 (Netherlands) - GCP - Web UIWeb UIUS - East1 (S. Carolina) - OSS - GCP - Web UIWeb UIEurope - West2 (London) - AWS - Web UIWeb UIUS - East1 (S. Carolina) - GCP - Web UIWeb UIAPAC - Central (Pune) - Azure - Web UIWeb UIAPAC - Asia East2 (Hong Kong) - GCP - Web UIWeb UIEurope - West1 (Ireland) - AWS - Web UIWeb UIEMEA - Israel (Tel Aviv) - AWS - Web UIWeb UIEurope - West (Netherlands) - Azure - Web UIWeb UIUS - West1 (California) - AWS - Web UIWeb UIAPAC - South1 (Mumbai) - AWS - Web UIWeb UIAPAC - South1 (Mumbai) - GCP - Web UIWeb UIEurope - West2 (London) - GCP - Web UIWeb UIUS - West2(Los Angeles) - GCP - Web UIWeb UISouth America - Brazil (São Paulo) - AWS - Web UIWeb UIUS - Central (lowa) - Azure - Web UIWeb UIAPAC - SouthEast2 (Sydney) - AWS - Web UIWeb UIUS - West1 (Oregon) - GCP - Web UIWeb UIAPAC - SouthEast Asia (Singapore) - Azure - Web UIWeb UIUS - West2 (Oregon) - AWS - Web UIWeb UIAPAC - East (New South Wales) - Azure - Web UIWeb UIUS - East (Virginia) - Azure - Web UIWeb UIEMEA - Israel (Tel Aviv) - Azure - Web UIWeb UICANADA - Central (Toronto) - Azure - Web UIWeb UIUS - East1 (N. Virginia) - AWS - Web UIWeb UIUS - East4 (N. Virginia) - GCP - Web UIWeb UIAPAC - NorthEast1 (Tokyo) - AWS - Web UIWeb UICANADA - Central - AWS - Web UIWeb UIUS - West (California) - Azure - Web UIWeb UIEurope - Central1 (Frankfurt) - AWS - Web UIWeb UI
Timeline of updates
- investigating
We are investigating cases of degraded performance for JFrog Cloud Platform customers. This is limited to a specific flow affecting the Set Me Up flow to generate a token affecting JFrog customers. We will provide more details within the next hour.
- resolved
This incident has been resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7e995eb0d587c3f6…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by JFrog, started 2025-04-01 13:50 UTC, resolved after 25 h, 2 update(s).
- Title
- JFrog Cloud Platform users might experience broken Set Me Up flow affecting subset of JFrog customers
- Vendor
- JFrog
- Date
- URL
- https://rewindex.com/company/jfrog/incidents/8spl4xb04l44
JFrog profileRecent JFrog incidentsAll outages on April 1, 2025JFrog in April 2025MarkdownJSON