Maintenance

Scheduled maintenance — zero uptime impact

If you need to power down, swap parts, or do any planned work, request a maintenance window from the Host dashboard at least 48 hours in advance.

Within that window:

• Meshive stops scheduling new pods onto your machine.
• Running pods are gracefully evicted (stopped) before your maintenance start time.
• Your uptime is not penalized for any downtime during the window.

When you finish, mark the machine as ready and pods will start flowing again.

You can also fill in a title and description for the window. These are surfaced to every client whose pod is affected, so a one-line “swapping the PSU, back by 3pm KST” goes a long way toward keeping the relationship friendly. If a client still wants to discuss timing, use the message feature on the machine page to negotiate the window before you confirm it.

Emergency maintenance — reduced uptime impact

Hardware does not always wait 48 hours. When you need to intervene immediately, toggle Emergency Maintenance on the dashboard before you start work.

In emergency mode, the downtime that occurs is counted at 1/10 of the normal rate against your uptime — i.e., the uptime hit is reduced to 10% of an unannounced outage. It is still better than nothing, so always toggle it on if you cannot wait.

Package updates — handled by Meshive

OS-level package updates are managed by the platform. The agent applies them automatically when:

• The machine is idle (no active pods), or
• The number of pending updates crosses an internal threshold, at which point we coordinate a safe time.

You do not need to run apt update yourself. Doing so manually is unnecessary and can conflict with the agent.

Driver updates — operator-pinned, pod-aware

NVIDIA driver versions are pinned cluster-wide by Meshive’s operations team after we verify a version is stable on production hardware.

When a new driver rollout reaches your machine, the agent will:

1. Wait for any active GPU pods to finish (or be re-scheduled).
2. Apply the new driver.
3. Bring the machine back into the pool.

This means you never have a driver mismatch with the rest of the network, and active client workloads are never killed by a driver upgrade.

IP changes — automatically reconnected

If your home or ISP IP address changes, the agent automatically detects it and reconnects via Tailscale. There is no need to log in and update anything. Dynamic-IP hosts are first-class citizens on Meshive.