Live
#18 medium manual
BlockedAgain
Opened 2026-07-26 16:49 UTC · Resolved 2026-07-26 16:50 UTC
Handoff Notes ← Dashboard
Timeline
OPENED
2026-07-26 16:49 UTC
Incident created manually. Severity: MEDIUM
CONTEXT AGGREGATED
2026-07-26 16:49 UTC
Sources available: 3/3 — Runbook: ✓ | Past incidents: ✓ | Infra health: ✓
Response Plan
2026-07-26 16:49 UTC

Severity

MEDIUM-HIGH: CPU 99% + memory 95% + upward trend; service degradation likely, full outage risk if unchecked.

Root Cause

  • Runaway process or memory leak consuming resources
  • Sudden traffic spike or cascading request queue buildup

Actions

  1. SSH to affected host; run top -b -n 1 | head -20 to identify top CPU/memory consumers.
  2. Kill or throttle the culprit process if identified; if unknown, restart the primary service gracefully.
  3. Check recent deployments, config changes, or traffic logs in last 30 minutes for trigger.
  4. Scale horizontally (add instances) or shed non-critical load immediately to relieve pressure.
  5. Confirm memory doesn't exceed 90% and CPU stabilizes below 85% within 5 minutes.

Watch

  • CPU trend and absolute value (target <80%; alert if >90%).
  • Memory usage (target <85%); watch for further creep toward OOM.

Escalate If

CPU remains >95% or memory >93% after 10 minutes of remediation attempts.

STATUS CHANGE
2026-07-26 16:50 UTC
OPEN -> RESOLVED (closed after validation; public manual form disabled and host pressure was transient)
Update Status
Details
ID #18
Severity MEDIUM
Source manual
Status RESOLVED
Opened 2026-07-26 16:49