FixOps
Play now
Linux Intermediate About 30 min +200 XP

Incident Notes Service Fails to Start

The internal incident notes service is down, leaving responders to coordinate the outage from chat scrollback.

Take this incident no signup All incidents

Stage 3 of 5 in Linux Outage Ladder.

Briefing

Storefront and API routing are healthy again, but the responders coordinating the rest of the outage are working from chat scrollback.

Its journal shows a clean stop at 00:14 for the maintenance window and nothing since.

The deploy responder needs the runbook stored in notesapp before stage 4 can begin.

Inspired by a real outage: Maintenance-window feature flag never reverted (FixOps composite of public postmortem patterns). Names and details are fictionalized.

The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.

How it plays

  1. 01

    Get paged

    The alert fires and the clock starts. Read the page and the briefing.

  2. 02

    Investigate

    Work in a simulated shell with realistic output: logs, configs, services.

  3. 03

    Fix it

    Change the system the way you would in production. Hints are there if you get stuck.

  4. 04

    Prove it

    Automated checks verify the recovery, then the debrief explains what happened.

All 61 incidents
Linux Beginner

Storefront Stuck in Maintenance Mode

Every Northstar Shops storefront page answers 503 with the maintenance banner, and checkout has taken no orders for 20 minutes.

+150 XP25 minStage 1/5

Networking Intermediate

Storefront API Calls Fail

Storefront pages load again, but cart, search and checkout calls through /api fail for every customer.

+210 XP30 minStage 2/5

Security Intermediate

Hotfix Deploy Blocked

The stabilization hotfix is staged, but deploy.service cannot be restarted to ship it.

+205 XP25 minStage 4/5

Your pager is ready.

Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.

Take this incident no signup Get it on Google Play