Incident Night is a survival game where you keep production alive from a 2 a.m. on-call page until the workday starts at 9, clearing wave after wave of alerts. This page explains the controls, the screen, commands and evolutions, the night's schedule and permanent upgrades.
Controls
- Phone: put your finger anywhere and drag. A stick appears where you touched and you move that way. Let go to stop
- Computer: WASD, arrow keys or hjkl to move, Esc (or P) to pause, R to hide the HUD for recording. You can also pick level-up cards with the 1–3 keys
- All your commands run automatically. All you do is keep from getting surrounded by alerts and go pick up resolved tickets
- Sound (music and effects) is on from the start. Toggle it with "Sound" on the title or pause screen
The screen
- Clock (top center): starts at 2:00 and moves one in-game minute per real second. Make it to 9:00, when your coworkers arrive, to win
- Uptime (under the clock): starts at 100.00% and drops when alerts touch you or the boss's or DB's projectiles hit you. Fall below the 99.0% SLA and it's "SLA Breached" — game over. The gauge goes green → yellow → red as it drops, and the edges of the screen turn red below 99.3%
- Experience bar (very top): fills as you pick up the resolved tickets that cleared alerts drop. Level up when it's full. Bigger light-blue and yellow tickets are worth more
- Command feed (bottom left): every time a command runs, a line like
$ grep -r ERROR /var/logscrolls by - Clear a lot at once and you'll see "Resolved ×N"
Leveling up and commands
When you level up, time stops and you choose one of three cards: a new command or passive (a skill that works just by having it), or an upgrade to one you already have. Everything goes up to Lv5 (Runbook stops at Lv2), and you can hold four commands and four passives.
| Command | How it works |
|---|---|
| grep | Fires a green laser the way you're moving, piercing every alert in a row (your first command) |
| Restart | Every few seconds, a big blast around you. The screen blinks dark for a moment |
| Rollback | A wave in every direction that pushes alerts back |
| Hotfix | Patches that home in on the nearest alert |
| Autoscale | Small servers orbit you, each shooting nearby alerts. They go down if swarmed and come back after a while |
| Rate Limit | Slows down alerts around you |
| Passive | Per level |
|---|---|
| Redundancy | Damage taken −10% |
| Runbook | Projectiles +1 (max Lv2) |
| CI/CD | Cooldown −8% |
| Coffee | Move speed +10% |
| Power Nap | Uptime recovers 0.01% per second |
| Monitoring Dashboard | Ticket pickup range +20% |
Evolutions
Get a command to Lv5 while holding its matching passive, and an evolution shows up among your next level-up cards (with a gold frame). Each level-up card lists its partner, and cards whose partner you already have glow green.
| Command Lv5 | + Passive | Evolution |
|---|---|---|
| grep | Monitoring Dashboard | Observability: four lasers sweep around you, scanning every direction |
| Restart | Redundancy | Zero-Downtime Deploy: a huge blast, then a few seconds of invincibility. No more blackouts |
| Autoscale | CI/CD | Kubernetes: up to 8 replicas. Downed ones heal themselves almost instantly |
| Hotfix | Runbook | Auto-Heal Script: each patch splits on hit and chains to more alerts |
Pickups
- Energy Drink: restores 30% of your uptime gauge. Timeouts often drop them
- Escalation: pulls in every resolved ticket on the screen. One is always lying near you at around 2:12
- Maintenance Mode: for 8 seconds, touching alerts doesn't cost you any uptime
The night's schedule
| Time | What happens |
|---|---|
| 2:00 | Your phone rings and the night begins. A handful of WARN alerts drift your way |
| 2:30– | Red 500 Internal Server Errors join in |
| 3:00 | "Alerts are triggering alerts": for one hour, every alert you clear splits into two WARNs |
| 3:30– | Memory leaks that grow over time. Leave them alone and they get tougher and hit harder |
| 4:00 | All the nightly batch jobs kick off at once, and WARNs pour in from the edges of the screen. Infinite loops that circle in on you start showing up |
| 4:30– | Slow, tough Timeouts (504) |
| 5:00 | Mid-boss: Boss: "Status Update?" Chases you while firing chat bubbles. Satisfy them by 6:30, or they head back to their next meeting |
| 6:00–7:00 | The morning traffic peak. A request flood of tiny alerts pours in as bands from the right, left and top. The busiest hour of the night |
| 7:30 | "A certificate expired": for 30 minutes the screen turns warning colors and alerts speed up |
| 8:00 | Boss: Production DB Down. A giant database fires SELECT * queries in every direction, bringing 500 errors along with it |
| 9:00 | Your coworker walks in — "Morning! Anything happen last night?" — and you win |
If the production DB is still down at 9:00, the clock freezes at 8:59 and you have 30 seconds to bring it back to win. Once the 30 seconds are up, your coworkers arrive, take over, and you win anyway. Once per run, if you're about to breach the SLA after 7:30, the SRE team joins the call and revives you (uptime refills to half the gauge, doesn't drop for 5 seconds, and nearby alerts get pushed away).
Score and On-call Pay
- Your score is alerts resolved × time kept up (minutes since 2:00) ÷ 10
- You earn 1 On-call Pay for every 10 alerts resolved and every 6 minutes kept up, plus 80 more for making it to 9:00
- The results screen is an Incident Report you can save as an image or share directly. It lists your lowest uptime, the main cause and the commands you ran
- Hit "Go study up" on the results screen to buy upgrades right away
Books & Study Groups (permanent upgrades)
From "Books & Study Groups" on the title screen, spend On-call Pay on upgrades that last for every night to come. Each goes up to Lv5 and costs 60, 120, 200, 320 and 480 (Design Review: 80, 160, 260, 380 and 520).
- Incident Drills: uptime buffer +10% (the same hit costs you less uptime)
- Postmortem Culture: damage +6%
- Shortcut-Key Study Group: move speed +5%
- Tech-Book Club: XP +8%
- Design Review: rerolls of level-up cards +1
On your first nights, you'll probably breach the SLA during the 6 a.m. morning traffic peak. Play a few runs, build up your upgrades and land one evolution, and you'll start making it to 9:00.
Characters
| Character | Traits | How to unlock |
|---|---|---|
| Junior Infra Engineer | Just getting started. Begins with grep | From the start |
| Veteran SRE | Begins with a stronger Restart. A bit tougher | Keep things running until 5:00 |
| Full-Stack Engineer | Begins with Hotfix. A bit faster, and earns a bit more XP | Resolve 1,000 alerts in total |
| CTO | Begins with Autoscale. Higher damage, uptime buffer, speed and range across the board — but now and then gets pulled into a board meeting and can't move for 4 seconds | Make it to 9:00 once |
Tonight's Incident (daily)
Each day, everyone plays the same night with the same character and the same alerts. The incident and the number of alerts depend on the weekday: Sundays are quieter, and Fridays — "cleaning up after a Friday release" — are the busiest. Your best score for the day shows on the title screen, so share your Incident Report on X and compare.
Alert Handbook and achievements
Alerts you run into and commands and evolutions you get go into the Alert Handbook, each with a one-line bit of on-call wisdom you'll probably recognize. There are 13 achievements, like reaching morning without uptime dropping below 99.99% or bringing the production DB back, and one of them is hidden until you unlock it. Your progress is saved only in your browser.