Vendor reports: operationalResolved · vendor status “resolved”Official status API

JFrog Cloud Platform users might experience broken Set Me Up flow affecting subset of JFrog customers

Reported by JFrog · Developer Tools & CI/CD · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Apr 1, 2025, 13:50 UTC
Vendor's clock
Resolved
Apr 2, 2025, 14:47 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 0 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • JFrog reports operational: "JFrog Cloud Platform users might experience broken Set Me Up flow affecting subset of JFrog customers".[E1, E2]
  • The vendor marked it resolved at 2025-04-02 14:47 UTC.[E3, E7]

Affected products and regions

  • Components: Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-04-02 14:47 UTC · summary s1, evidence 266f6a5f4d997b07

Evidence (7)
  1. E1JFrog reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "JFrog Cloud Platform users might experience broken Set Me Up flow affecting subset of JFrog customers". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-04-01 13:50 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-04-02 14:47 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI, Web UI

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

JFrog is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Apr 1, 2025, 13:50 UTCVendor-reported startVendor time
  2. Apr 2, 2025, 14:47 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.