Vast.ai Workload Recovery Runbook

Overview

Protect people and credentials first, then preserve recoverable data, stop uncontrolled spend, and restore service from an external checkpoint or last-known-good template. Provider states imply different actions and must not be collapsed into retry.

Prerequisites

• Severity, start time, affected instances/endpoints, release, and user impact
• Last verified external checkpoint or Serverless template
• Incident commander, data owner, billing owner, and authority for stop/destroy/rollback

Instructions

Step 1: Stabilize identity and scope

Confirm account/team context, affected IDs, current state, balance, and whether a credential or data exposure is involved.

Step 2: Classify the provider state