Hetzner incident
Planned maintenance for leaf nbg1-cloud1-leaf63
Hetzner experienced a minor incident on May 5, 2026 affecting Cloud, lasting 20h 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 05, 2026, 11:21 AM UTC
We would like to inform you of an upcoming maintenance operation on central network components of our cloud infrastructure. The maintenance is scheduled for 2026-05-05 10:45:00 +0200 and is expected to take approximately one hour. Due to a critical software update, it is necessary to upgrade the network components to a new version. Because of an incompatibility between the versions, the updates on the redundant switches must be carried out simultaneously. As a result, despite the redundant network setup, a temporary unavailability of the affected services during the maintenance window cannot be avoided. During the maintenance period, cloud servers and volumes connected to the respective network component will be unreachable. We strongly recommend unmounting and detaching all affected volumes before the maintenance period begins in order to prevent potential data inconsistencies. Thank you for your understanding. Should you have any questions, we will be happy to assist you.
- monitoring May 05, 2026, 12:17 PM UTC
We would like to inform you of an upcoming maintenance operation on central network components of our cloud infrastructure. The maintenance is scheduled for 2026-05-05 10:45:00 +0200 and is expected to take approximately one hour. Due to a critical software update, it is necessary to upgrade the network components to a new version. Because of an incompatibility between the versions, the updates on the redundant switches must be carried out simultaneously. As a result, despite the redundant network setup, a temporary unavailability of the affected services during the maintenance window cannot be avoided. During the maintenance period, cloud servers and volumes connected to the respective network component will be unreachable. We strongly recommend unmounting and detaching all affected volumes before the maintenance period begins in order to prevent potential data inconsistencies. Thank you for your understanding. Should you have any questions, we will be happy to assist you.