Changes / JFrog / JFrog Cloud Platform Unavailable (UI only) For Some Customers Due to Login Issues
JFrog: Critical incident: JFrog Cloud Platform Unavailable (UI only) For Some Customers Due to Login Issues
Summary
JFrog reported a critical UI-login outage for some customers in APAC - SouthEast1 (Singapore) - AWS, Europe - West2 (London) - GCP, and US - West (California) - Azure. It started 2025-03-05 13:49 UTC and was resolved at 2025-03-05 14:42 UTC (52 min); JFrog reported implementing a fix.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: JFrog Cloud Platform Unavailable (UI only) For Some Customers Due to Login Issues
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2025-03-05 13:49 UTC
Before: not present
After: 2025-03-05 14:42 UTC
Before: not present
After: APAC - SouthEast1 (Singapore) - AWS - Web UI, Europe - West2 (London) - GCP - Web UI, US - West (California) - Azure - Web UI, Web UI
Before: not present
After: We are investigating an availability issue that is impacting some JFrog Cloud Platform customers. Should Impact only UI logins. We will provide more details within the next hour.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: We are currently investigating this issue.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: JFrog Cloud Platform Unavailable (UI only) For Some Customers Due to Login Issues (this change) JFrog reported a critical UI-login outage for some customers in APAC - SouthEast1 (Singapore) - AWS, Europe - West2 (London) - GCP, and US - West (California) - Azure. It started 2025-03-05 13:49 UTC and was resolved at 2025-03-05 14:42 UTC (52 min); JFrog reported implementing a fix. | Major incident |