JFrog: SLA evidence report
JFrog: SLA evidence report
We hold no probe record for JFrog: we read its status page, so the only incident record here is what JFrog declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents JFrog declared
- 4
- On its own status page, in this window.
- Window
- 2026-09-23 to 2026-10-23
- UTC, 30 days.
Sep 30, 2026, 7:07 PM UTC to Sep 30, 2026, 9:39 PM UTC
Potential slowdown on Maven remotes in AWS Europe Central, impact minor
Oct 8, 2026, 11:13 AM UTC to Oct 8, 2026, 1:13 PM UTC
JFrog Cloud Platform - Xray Service Disruption in Azure US East, impact major
Oct 18, 2026, 7:08 AM UTC to Oct 18, 2026, 9:40 AM UTC
JFrog Cloud Platform - Multiple Service Disruptions in Azure Southeast Asia, impact critical
Oct 20, 2026, 6:04 AM UTC to Oct 20, 2026, 12:10 PM UTC
JFrog Cloud Platform - Multiple Service Disruptions in GCP Europe West, impact critical
Methodology
These incidents come from JFrog's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit JFrog owes, if any, is decided under its own SLA.