Status Code Drinking Game

200 sip, 404 drink, 500 finish - the internet's error pages, weaponized.

Also known as: HTTP Status Code Drinking Game · 404 Drinking Game · Developer Drinking Game

Be the first to rate this game

Your rating:

Players 2-12

You needThe free code deck below (or any screen with logs), drinks

DrinkAnything

Intensity

Time15-45 min

Play Status Code Drinking Game online

The Status Code Drinking Game turns the internet's error pages into a party. Every web request that has ever loaded (or failed to load) came back with a three-digit HTTP status code - 200 OK when everything works, 404 Not Found when it doesn't, 500 Internal Server Error when something is on fire and nobody knows why. This game hands each of those codes a drinking rule: the 200s are calm sips, the 300s shuffle drinks and seats around the table, the 400s punish individual players for their own bad requests, and the 500s take the whole table down with the server.

You don't need to know anything about computers to play - the deck below explains every card as it deals it, and half the rules are just seat swaps, forbidden words and races dressed up in nerd clothing. But if your group does ship software for a living, this is the definitive tech-team game night: play it card-deck style at the table, or go full log mode and drink to the live status codes scrolling off a real dashboard. Either way, when a 418 I'm a Teapot comes up, you pose.

What you need & setup

Everyone gets a drink and sits where they can see one shared phone or screen.
Open the free code deck below - it deals a random status code with its rule each round.
Pick a dealer to read each code aloud with maximum server-room gravitas; rotate every round.
Agree on the standing severity ladder before you start: 2xx sip, 3xx redirect, 4xx drink, 5xx everyone drinks.
Optional log mode for tech crews: put a real (non-production!) request log or status dashboard on the TV instead.

How to play Status Code Drinking Game

Learn the severity ladder

The whole game hangs on one idea every player can learn in ten seconds: the higher the status code, the worse your night. A 2xx card means success - a calm sip, a toast, a moment of peace. A 3xx card redirects: drinks, seats or penalties get moved to somebody else. A 4xx card is a client error - one specific player messed up and pays for it. A 5xx card is a server error - the infrastructure failed, so the whole table drinks together. Once the group knows the ladder, every card is instantly legible even if nobody has heard of the code on it.

Deal a code each round

Going clockwise, each player taps the deck below to draw a status code and reads it out - number, name, then the rule. The drawer is the 'client' for that round: when a card says the drawer does something, that's them. Resolve the card, laugh at whoever it hit, and pass the phone left. Rounds take thirty seconds, so the deck moves fast; a full lap of the table is a nice natural checkpoint for water and refills.

Resolve 4xx cards on the guilty

Client-error cards name their own victim: 400 Bad Request punishes whoever asks a question, 401 Unauthorized locks a player out until the table 'authenticates' them, 403 Forbidden creates a banned word, and 404 Not Found hunts down the player who is slowest to react. These are the game's engine - they build running rules that stack on top of each other, so by round ten the table is a minefield of forbidden words and unauthorized players, exactly like a real codebase.

Fear the 5xx cards

Server errors are the group-punishment cards, and the deck's real drama. 500 Internal Server Error is the classic - everyone drinks, no explanation given, because there never is one. 502 Bad Gateway makes your upstream neighbor drink on your behalf, 503 Service Unavailable takes the drawer 'down for maintenance' (they skip a turn but drink double when they return), and 504 Gateway Timeout is a table-wide race where the slowest responder pays. When two 5xx cards land back to back, tradition demands someone mutter 'check the logs.'

Honor the 418

418 I'm a Teapot is the sacred card. Whoever draws it must strike a teapot pose - one arm the handle, one arm the spout - and the last player to copy the pose drinks twice, short and stout. This rule is non-negotiable in every known deployment of the game. It exists because in 1998 the internet's engineers wrote a joke error code into an April Fools document, and the joke has now outlived several real technologies.

Or run log mode

For developer game nights: skip the deck and put a real status dashboard, staging-environment log tail or synthetic-traffic monitor on the shared screen. Apply the standing ladder to whatever scrolls past - sip on 2xx bursts, drink on every 404, finish on a genuine 500. Set a per-minute cap before you start, because one bad crawler can hit a missing page forty times in ten seconds and the game must never outrun good sense. Never, ever play log mode against production during an actual incident - that's not a game, that's a cry for help.

The rules

Severity ladder: 2xx codes are sips, 3xx codes redirect drinks or seats, 4xx codes punish one player, 5xx codes hit the whole table.
Draw one status code per round, going clockwise; the drawer is the 'client' and reads the card aloud before resolving it.
200 OK: everyone takes one calm, well-earned sip. Enjoy it - the errors are coming.
301 Moved Permanently: everyone moves one seat to the left and drinks in their new home; the seating change is permanent.
403 Forbidden: the drawer bans one common word until the next 403 is drawn; saying it costs a drink each time.
404 Not Found: last player to put a hand on their head 'was not found' and drinks twice.
418 I'm a Teapot: the drawer strikes a teapot pose; the last player to copy it drinks twice.
429 Too Many Requests: whoever has talked the most this round drinks - the table is the rate limiter and its ruling is final.
500 Internal Server Error: everyone drinks. No explanation is given. There never is.
Standing rules (bans, authorizations, seat changes) stack until the deck clears them - keep a mental changelog or pay the price.

Variations & house rules

Log Mode

The developer's version: replace the deck with a live status dashboard or log tail from a staging or demo environment and apply the ladder to real traffic - sip on 2xx, drink on 404, finish on 500, toast anyone who somehow triggers a 418. Cap it at a fixed number of drinks per minute and pre-agree which codes count, because real logs are burstier than any deck. Absolutely never play against production or during a real incident.

On-Call Roulette

One player per round is designated 'on call' before the card is drawn. Whatever the card's penalty, the on-call player takes it alongside the actual victim - they were paged, so they suffer too. Rotate the pager clockwise. This variation is unreasonably popular with people who have actually carried a pager, for reasons best described as processing.

REST in Peace

Elimination format: each player has three 'retries.' Every drink a card assigns you costs a retry (you still drink). Lose all three and you are deprecated - out of the round, but you may heckle as legacy code. Last supported player wins. Fast, brutal, and best as a one-lap finale once the standard game has warmed the table up.

Cache Rules Everything Around Me

Add one meta-rule: whenever a card repeats a code the table has already seen tonight, it is 'cached' - the original victim of that code drinks instead of whoever the card names now. Rewards the one friend who remembers everything and turns the late game into a memory gauntlet worthy of a word game.

Sober Status

The zero-alcohol build: sips become points scored against you, 5xx cards give everyone a point, and the lowest score after three laps wins. All the poses, seat swaps, banned words and races survive intact - which proves what players always suspect: the drinking was never the funny part. Perfect for office game nights where HR is also playing.

Pro tips

Read the code name aloud every time, even late in the night - 'four-oh-four, not found' is half the comedy and keeps non-technical players fully in the game.

Keep the standing-rule count honest: two or three active bans and authorizations is funny; seven is homework. Let a 200 OK clear the board if the table is drowning.

Seat your most theatrical friend as the first dealer - the game lives or dies on whether 500 Internal Server Error is announced like a sea captain reporting an iceberg.

In log mode, pick the screen before anyone drinks: a quiet staging environment gives a chill game, a synthetic-traffic demo gives chaos. Decide which night you're having.

Mixed table of devs and civilians? Pair them for the first lap - every card gets one person who knows the joke and one who makes it funnier by asking what a gateway is.

The 418 pose is mandatory. If someone refuses to be a teapot, the deck has spoken: two drinks and the table hums the song anyway.

Where Status Code Drinking Game fits on the shelf

Status Code Drinking Game is one of the gentler picks on the shelf - 12th of 12 screen games by intensity, rated 2 out of 5.
It is one of the few games here that genuinely works with just 2 players, and it stays fun up to 12.
A typical session runs 15-45 min - a solid middle act for the evening.
Browse the full tv, movie & music games shelf to compare all 12 games side by side.

A little history

The status codes themselves date to the earliest HTTP specifications in the 1990s, and turning them into a drinking game is a tradition that grew out of startup launch nights, hackathons and on-call retros wherever engineers and beer shared a room - watching a deploy dashboard is already a spectator sport, so attaching sips to the error stream was inevitable. The 418 I'm a Teapot code, an April Fools joke from 1998 that the internet refused to let die, is the patron saint of the game. No single author exists to credit; like every good error, it emerged in production.

Drink responsibly: The 5xx cards concentrate group drinks, and log mode can burst far faster than any card deck - so cap drinks per minute, pour light, and keep water in every player's reach. Skip rules always apply: anyone can convert any penalty to a pass without explanation. Keep log mode away from real incidents and real production systems, never pressure anyone to drink, and shut the game down like a graceful server: drain connections, hydrate, and return everyone a 200. See our safety guide for pacing tips and alcohol-free versions.

Status Code Drinking Game FAQ

What is the status code drinking game?

It's a party game where HTTP status codes - the three-digit responses websites send, like 404 Not Found or 500 Internal Server Error - each carry a drinking rule. Success codes (2xx) mean gentle sips, redirects (3xx) move drinks and seats around, client errors (4xx) punish one player, and server errors (5xx) make the whole table drink. You can play with the free card deck on this page or, for tech crews, against a real log dashboard.

Do I need to know programming to play?

Not at all. Every card in the deck explains its own rule in plain language - the status codes are just theming on top of classic party mechanics like seat swaps, forbidden words, reaction races and group toasts. Non-technical players usually end up loving the 418 teapot card hardest of anyone at the table.

What does 404 mean in the game?

404 Not Found is the deck's signature reaction card: when it's drawn, the last player to put a hand on their head 'was not found' and drinks twice. In log mode, every real 404 scrolling past the screen costs the table a drink - which is why you cap drinks per minute before pointing the game at a website with broken links.

How do we play with real logs safely?

Use a staging, demo or synthetic-traffic environment - never production, and never during a real incident. Agree in advance which codes count, set a hard cap of a few drinks per minute, and appoint one sober-ish referee to pause the feed when traffic bursts. Real logs are far spikier than a card deck, so the cap is what keeps log mode a game instead of a hazard.

Can we play without alcohol?

Yes - the Sober Status variation swaps sips for penalty points and keeps every pose, ban and race intact. It works well as an office or hackathon game where drinking isn't on the table, and the 500-means-everyone-scores rule stays exactly as unfair as it should be.

Status Code Drinking Game

Play Status Code Drinking Game online

What you need & setup