Runbook: Application Down
Trigger
Use this runbook when the web application, dashboard, or public site is unavailable or returning widespread errors.
Immediate Actions
| Step | Action | Owner | Evidence | Status |
|---|---|---|---|---|
| 1 | Confirm user impact and affected URL | Incident Commander | URL and screenshot | TBD |
| 2 | Check Cloudflare Pages / deployment status if the affected service is documentation | Operations | Cloudflare deployment screenshot | TBD |
| 3 | Check Laravel Forge server status for application servers | Operations | Forge screenshot | TBD |
| 4 | Check application logs and Sentry for critical errors | Backend / Operations | Sanitized log or Sentry issue | TBD |
| 5 | Check database, Redis, queue workers, and Nginx health where applicable | Operations | Health evidence | TBD |
| 6 | Assign severity and incident owner | Incident Commander | Incident note | TBD |
Recovery Checks
| Check | Expected Result |
|---|---|
| Homepage or dashboard | Loads successfully |
| Login | Works |
| Protected API endpoint | Works |
| Queue workers | Processing jobs |
| Sentry | No new critical errors |
| Logs | No recurring fatal error |
Escalation
Escalate as SEV-1 if production users cannot access the core platform, login is down, or the issue affects payments, wallets, or student data.