An incident-response problem bank for DevOps, SRE, and infrastructure engineers

4,874 incidents.
Solve them yourself, from root cause to prevention.

CrashLoopBackOff, DNS resolution failures, permission errors, deploys that went green but never shipped — read real-world incidents as scenarios and write the cause, recovery, and prevention yourself.

  • Solve without signing up
  • 1,280 free problems
  • Today's problem includes the model answer
Today's problem· free for today only
Linux Intermediate 19 min

The application cannot read files

A scenario that narrows down the root cause, centered on checking permissions, owner, and the execution account together, in the situation of the application being unable to read files because permissions changed after a deploy script.

Look at first
  • Identify the primary failure signal in the Permission Audit scenario.
  • Separate visible symptoms from the underlying technical dependency.

Write recovery and prevention on the next screen; the model answer opens when you submit.

How it works

1

Read the scenario

Gauge the blast radius from the logs and symptoms

2

Write three answers

Cause analysis · Recovery plan · Prevention

3

Compare with the model answer

See the signals and ordering you missed

Problems by area

Pricing

Free
₩0
  • 1,280 free problems
  • Submit without signing up
  • First hint per problem when logged in
  • Explanations for today's problem and quick quizzes
Pro

Bank transfer · no auto-renewal · full refund within 7 days if unused

  • All 4,874 problems
  • Every hint
  • Model answer after you submit
Start Pro

Start with the incidents people get stuck on

See all 31 guides