ChangesJFrogJFrog Cloud Platform - Multiple Service Disruptions in Azure Southeast Asia
JFrog: Incident updated: JFrog Cloud Platform - Multiple Service Disruptions in Azure Southeast Asia
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what JFrog removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
Archive proof
Rewindex commits each version of an incident to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured 07:43 UTC
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
bd3f620817a24e67…After captured 08:13 UTC
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
52dcca6447ef44a5…
History of this incident
YesterdaySunday, October 18Sun, Oct 18
1 rewrite, 3 incident changes
- Normal progressIncident
- Normal progressIncident
Incident updateJFrog Cloud Platform - Multiple Service Disruptions in Azure Southeast Asiathis change
- Minor editEdited by the vendor
JFrog Cloud Platform - Multiple Service Disruptions in Azure Southeast Asia
JFrog corrected the incident start time from 2026-10-18 07:31 UTC to 2026-10-18 07:08 UTC. The incident affected multiple customers in Azure Southeast Asia with degraded Artifactory and Xray services; it remained open when archived (open for 0 min at the last update), with investigation ongoing and no cause or fix stated.
- OutageCritical incident
JFrog Cloud Platform - Multiple Service Disruptions in Azure Southeast Asia
JFrog reported a critical incident starting 2026-10-18 07:31 UTC, with degraded Artifactory and Xray services affecting multiple customers in Azure Southeast Asia (Singapore). It remained under investigation and still open when archived, open for 0 min at the last update; no cause or fix was stated.