Replit Incident Runbook

Overview

Restore a Replit published app without turning an outage into a data, credential, or billing incident. Separate a Replit platform event from an application regression, keep evidence allowlisted, and use only a recovery action that the owner approved before the incident.

Prerequisites

• The published replit.app hostname, incident identifier, impact statement, and owner-defined severity policy.
• Read-only access to Publishing status, logs, monitoring, and the source revision.
• A named incident commander, communications owner, and production-data owner.
• The last verified release, migration state, and a tested rollback or fix-forward path.
• Approval requirements for republishing, changing deployment type/capacity, rotating Secrets, or modifying production data.

Instructions

Step 1 — Establish impact and freeze unrelated changes

Record the failing user journey, first-seen time, affected population, and current deployment version. Pause unrelated releases. Do not change capacity, DNS, access, Secrets, or data while the failure domain is unknown.