Scheduled Maintenance Proxmox Cluster Reboot Status: Resolved
Priority - Critical Affecting Server - dylan.protectedserver.net

Date: Sunday, April 19, 2026 Time: 8:00 AM GMT-5  · :13:00 UTC (April 19) Expected duration: Approximately 5–15 minutes per node (rolling)

Objective

We will be performing a scheduled reboot of our Proxmox virtualization cluster to apply network-level improvements. The goals of this maintenance are:

  • Increase network resilience across the cluster, reducing the risk of connectivity interruptions
  • Resolve a bond configuration issue identified on the cluster's network interfaces

Expected impact

Each node in the cluster will be rebooted sequentially. Services hosted on a node being rebooted may experience a brief interruption of approximately 5 to 15 minutes while that node comes back online. Services on other nodes will continue running normally throughout the window.

What you need to do

No action is required on your part. We recommend avoiding scheduled deployments or large operations during the maintenance window.

Status updates

We will post real-time updates on our status page and notify you once maintenance has been completed successfully.

We appreciate your patience as we continue improving the reliability of the RemarkableCloud platform.

✅ Maintenance done. Proxmox cluster is back, network is stronger, bond issue squashed. All services online.

Thanks for bearing with us

Scheduled Maintenance - Proxmox Cluster Reboot Status: Resolved
Priority - Critical Affecting Server - Tenantos

Date: Sunday, April 19, 2026 Time: 8:00 AM GMT-5 · 13:00 UTC (April 19) Expected duration: Approximately 5–15 minutes per node (rolling)

Objective

We will be performing a scheduled reboot of our Proxmox virtualization cluster to apply network-level improvements. The goals of this maintenance are:

  • Increase network resilience across the cluster, reducing the risk of connectivity interruptions
  • Resolve a bond configuration issue identified on the cluster's network interfaces

Expected impact

Each node in the cluster will be rebooted sequentially. Services hosted on a node being rebooted may experience a brief interruption of approximately 5 to 15 minutes while that node comes back online. Services on other nodes will continue running normally throughout the window.

What you need to do

No action is required on your part. We recommend avoiding scheduled deployments or large operations during the maintenance window.

Status updates

We will post real-time updates on our status page and notify you once maintenance has been completed successfully.

We appreciate your patience as we continue improving the reliability of the RemarkableCloud platform.

✅ Maintenance done. Proxmox cluster is back, network is stronger, bond issue squashed. All services online.

Thanks for bearing with us

Scheduled Maintenance Window – Proxmox Cluster Upgrade Status: Resolved
Priority - Critical Affecting System - All Virtual and Shared Servers

Date and Time: January 10, 2026, at 3:00 PM (GMT -5)
Duration: 2 hour
Expected Downtime: Approximately 15 minutes during node reboots
Purpose:
We will be performing a scheduled maintenance window to upgrade our Proxmox Cluster to the latest stable specifications. This upgrade ensures improved performance, security, and reliability for our infrastructure.
Impact:
All nodes will be rebooted during the process, resulting in an estimated downtime of 15 minutes. Please plan accordingly to minimize any disruption to your operations.
Thank you for your understanding and cooperation.
If you have any questions or concerns, please contact the IT team.

Service Notice: S3 Backup Cluster Outage Status: Resolved
Priority - Critical Affecting System - s3 Storage for customer'sbackups

We are currently experiencing an outage in our S3 backup cluster, which is used exclusively for storing customer backups.

During this time, it is not possible to access, back up, or restore data via JetBackup. Our internal backup systems remain fully operational and unaffected.

We are actively working to resolve the issue as quickly as possible and will keep you updated.

Thank you for your patience and understanding.