System instability xeon5,6,7,8 on 7 Jul 2026 14:04:04 (UTC+00:00)
Resolved on 8 Jul 2026 03:51:36 (UTC+00:00)
Resolved - 19:02 CEST
The incident has been marked as resolved because all affected systems are operational again. We will continue monitoring the situation to confirm everything remains stable. If your VM is still experiencing issues, please contact support.
Monitoring - 15:41 CEST
The fix has been applied, and the affected KVM servers are coming back online. We are monitoring the nodes to confirm everything remains stable.
Identified - 15:28 CEST
We identified the instability on xeon5, xeon6, xeon7, and xeon8 after the CPU type change. We are reverting that change and applying the new Proxmox kernel to resolve the issue.
Reported - 15:23 CEST
We detected instability on xeon5, xeon6, xeon7, and xeon8 after the CPU type change and started investigating immediately.
Resolved - 19:02 CEST
The incident has been marked as resolved because all affected systems are operational again. We will continue monitoring the situation to confirm everything remains stable. If your VM is still experiencing issues, please contact support.
Monitoring - 15:41 CEST
The fix has been applied, and the affected KVM servers are coming back online. We are monitoring the nodes to confirm everything remains stable.
Identified - 15:28 CEST
We identified the instability on xeon5, xeon6, xeon7, and xeon8 after the CPU type change. We are reverting that change and applying the new Proxmox kernel to resolve the issue.
Reported - 15:23 CEST
We detected instability on xeon5, xeon6, xeon7, and xeon8 after the CPU type change and started investigating immediately.
Monitoring on 7 Jul 2026 14:04:04 (UTC+00:00)
Monitoring - 15:41 CEST
The fix has been applied, and the affected KVM servers are coming back online. We are monitoring the nodes to confirm everything remains stable.
Identified - 15:28 CEST
We identified the instability on xeon5, xeon6, xeon7, and xeon8 after the CPU type change. We are reverting that change and applying the new Proxmox kernel to resolve the issue.
Reported - 15:23 CEST
We detected instability on xeon5, xeon6, xeon7, and xeon8 after the CPU type change and started investigating immediately.
Monitoring - 15:41 CEST
The fix has been applied, and the affected KVM servers are coming back online. We are monitoring the nodes to confirm everything remains stable.
Identified - 15:28 CEST
We identified the instability on xeon5, xeon6, xeon7, and xeon8 after the CPU type change. We are reverting that change and applying the new Proxmox kernel to resolve the issue.
Reported - 15:23 CEST
We detected instability on xeon5, xeon6, xeon7, and xeon8 after the CPU type change and started investigating immediately.