Outage Guide

Claude Outage Playbook: Keep Critical Work Moving

Treat Claude outages like any reliability incident: verify, mitigate, communicate, and recover.

Unknown

Live probe summary for Claude (updates every 60s on this page)

Latency

--

HTTP

--

Region

--

Checked

--:--:-- UTC

Fresh probeRefreshing…

Last updated: 2026-02-27

Mitigation priorities

  • Protect SLA-sensitive workflows first.
  • Switch from diagnosis mode to continuity mode quickly.
  • Use a known-good backup path, not ad-hoc experiments.

Recovery checklist

  1. Validate completion latency before full workload migration back.
  2. Replay queued prompts in batches.
  3. Document what failed and what fallback worked.

Related pages

5-Minute Decision Matrix

SignalLikely MeaningAction Now
Claude unavailable for most usersPlatform incident likelySwitch critical flows to backup and communicate ETA uncertainty.
Only specific account/session affectedAuth/session issue likelyRe-authenticate once and retry in private mode.
Claude slow but not fully downDegraded performanceThrottle non-critical tasks and reroute priority tasks.

Incident Update Template (Copy/Paste)

[Incident update] Claude reliability issue

- Current impact: [blocked/degraded] workflows
- Scope: [team/service/region]
- Verification: live monitor + official status check completed
- Mitigation: switched critical tasks to backup assistant
- Next check-in: [UTC time in 5-10 minutes]

Evidence Checklist Before Escalation

  • Exact timestamp (UTC) and affected workflow.
  • Error message or symptom pattern (with screenshot if relevant).
  • Whether issue reproduces across browser/network/device.
  • Current live status signal and official status reference.
  • Temporary workaround status (backup provider: ChatGPT, Gemini, Midjourney).

Related Articles