Resolved after 33 minutes, affecting berrybyte Status - Incident history service, on May 12, 2026.
Type: Incident Duration: 21 minutes May 12, 04:54:49 GMT+0 Postmortem - On 2026-05-12 at approximately 04:02 UTC, the `rene: vps-dfw-7950X` hypervisor became unreachable due to a kernel fault on the host. The host was recovered via power cycle and all VMs returned to service automatically. **Timeline (UTC)** * 04:02 - Hypervisor (and subsequent VMs) stopped responding to network and console. * 04:07 - NOC alerted; investigation began. * 04:16 - Out-of-band investigation confirmed the host was wedged at the kernel level and not recoverable in software. * 04:25 - Host was forcefully power-cycled. Boot and VM auto-start completed within a few minutes. * 04:29 - All VMs confirmed running. We've identified the kernel condition that caused the host to hang and applied a configuration change to prevent it from recurring. Additional monitoring has been added to detect early warning signs of this class of issue across our fleet. We're sorry for the disruption. If you're still experiencing issues with your VM, please contact support and we'll take a look.. May 12, 04:41:53 GMT+0 Resolved - This incident has been resolved.. May 12, 04:32:34 GMT+0 Monitoring - We implemented a fix and are currently monitoring the result.. May 12, 04:20:58 GMT+0 Investigating - We are currently investigating this incident..
Affected components
Update timeline
- postmortem May 12, 2026, 04:54 AM UTC
Type: Incident Duration: 21 minutes May 12, 04:54:49 GMT+0 Postmortem - On 2026-05-12 at approximately 04:02 UTC, the `rene: vps-dfw-7950X` hypervisor became unreachable due to a kernel fault on the host. The host was recovered via power cycle and all VMs returned to service automatically. **Timeline (UTC)** * 04:02 - Hypervisor (and subsequent VMs) stopped responding to network and console. * 04:07 - NOC alerted; investigation began. * 04:16 - Out-of-band investigation confirmed the host was wedged at the kernel level and not recoverable in software. * 04:25 - Host was forcefully power-cycled. Boot and VM auto-start completed within a few minutes. * 04:29 - All VMs confirmed running. We've identified the kernel condition that caused the host to hang and applied a configuration change to prevent it from recurring. Additional monitoring has been added to detect early warning signs of this class of issue across our fleet. We're sorry for the disruption. If you're still experiencing issues with your VM, please contact support and we'll take a look.. May 12, 04:41:53 GMT+0 Resolved - This incident has been resolved.. May 12, 04:32:34 GMT+0 Monitoring - We implemented a fix and are currently monitoring the result.. May 12, 04:20:58 GMT+0 Investigating - We are currently investigating this incident..
Your product runs on more than BerryByte
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services