replit-incident-runbook

name	replit-incident-runbook
description	Execute Replit incident response: triage deployment failures, database issues, and platform outages. Use when responding to Replit-related outages, investigating deployment crashes, or running post-incident reviews for Replit app failures. Trigger with phrases like "replit incident", "replit outage", "replit down", "replit emergency", "replit broken", "replit crash".
allowed-tools	Read, Grep, Bash(curl:*)
version	1.12.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","replit","incident-response","debugging"]
compatibility	Designed for Claude Code

Replit Incident Runbook

Overview

Rapid incident response for Replit deployment failures, database issues, and platform outages. Covers triage, diagnosis, remediation, rollback, and communication.

Prerequisites

• Access to Replit Workspace and Deployment settings
• Deployment URL for health checks
• Communication channel (Slack, email)
• Rollback awareness (Deployment History)

Severity Levels

Level	Definition	Response Time	Examples
P1	Complete outage	< 15 min	App returns 5xx, DB down
P2	Degraded service	< 1 hour	Slow responses, intermittent errors
P3	Minor impact	< 4 hours	Non-critical feature broken
P4	No user impact	Next business day	Monitoring gap

Quick Triage (First 5 Minutes)

set -euo pipefail
DEPLOY_URL="https://your-app.replit.app"

echo "=== TRIAGE ==="

# 1. Check Replit platform status
echo -n "Replit Status: "
curl -s https://status.replit.com/api/v2/summary.json | \
  python3 -c "import sys,json;print(json.load(sys.stdin)['status']['description'])" 2>/dev/null || \
  echo "Check https://status.replit.com"

# 2. Check your deployment health
echo -n "App Health: "
curl -s -o /dev/null -w "HTTP %{http_code} (%{time_total}s)" "$DEPLOY_URL/health" 2>/dev/null || echo "UNREACHABLE"
echo ""

# 3. Get health details
echo "Health Response:"
curl -s  2>/dev/null | python3 -m json.tool 2>/dev/null ||  


 -n 
curl -s -o /dev/null -w