supabase-incident-runbook

# Supabase Incident Runbook ## Overview When a Supabase-backed application experiences failures, you need a structured response: verify the Supabase platform status, check your connection pool, inspect `pg_stat_activity` for stuck queries, debug RLS policies that silently filter data, review Edge Function execution logs, verify storage bucket health, and escalate to Supabase support with a complete evidence bundle. This runbook covers every layer from the SDK client through the database to platform services. **When to use:** Production errors involving Supabase, degraded API response times, connection pool exhaustion, silent data filtering from RLS, Edge Function cold start failures, or storage upload/download errors. ## Prerequisites - Supabase project with dashboard access at [supabase.com/dashboard](https://supabase.com/dashboard) - `@supabase/supabase-js` v2+ installed in your project - Supabase CLI installed for Edge Function log access - Direct database connection string (for `psql` diagnostics) - Access to [status.supabase.com](https://status.supabase.com) for platform health ## Instructions ### Step 1: Triage — Platform vs. Application Determine whether the issue is a Supabase platform incident or an application-level bug. Check platform status first, then verify your SDK client connectivity. **Check Supabase platform status:** ```bash # Check official status page curl -sf https://status.supabase.com/api/v2/status.json | jq '{ indicator: .status.indicator,...