Some systems are under maintenance.
Status of AS200462
Last updated 2025-09-26 20:44:59
Last updated 2026-02-19 20:05:57
Last updated 2025-09-18 17:23:01
Last updated 2026-02-26 16:47:44
Last updated 2026-03-04 18:09:09
Last updated 2026-02-23 17:48:34
Last updated 2026-02-26 15:52:25
Last updated 2026-02-07 12:51:18
Last updated 2026-02-26 18:10:16
Last updated 2026-02-27 23:28:12
Last updated 2026-02-24 12:15:45
Last updated 2026-02-22 20:49:41
Last updated 2025-11-11 22:18:39
Last updated 2025-09-18 17:23:01
Last updated 2025-10-23 12:38:37
Last updated 2025-09-18 17:23:01
Last updated 2025-09-18 17:23:01
Last updated 2025-09-18 17:23:01
Last updated 2025-09-18 17:23:01
Last updated 2025-09-18 17:23:01
The incident has been resolved.
Upstream confirmed the issue and is preparing a hotfix.
Upstream is checking for logic errors on backup creation.
Enduser capability to create new backups has been restored, but may still be impacted from inconsistency. The recommendation to create backups from within VPS itself remains in place.
Enduser capability to restore backups remain disabled. Please check with support in case a restore is required.
We are currently observing a faulty patch from virtualization upstreams on the backup logic which falsely interprets an exit code from a sanity check, leading to potential inconsistency of created backups. From current log validation, only a small subset of VMs are impacted by this.
A ticket with the upstream has been opened and we are awaiting feedback.
For the moment, end-user capability to create and restore backups have been disabled. Scheduled weekly backups continue to run normal, but may be impacted from the same bug. We suggest users create their own backup from within the systems to be on the safe side.
In case a restore of such automatic backup is needed, please open a support ticket and we will validate the consistency before initiating a restore.