Everyone gets a drink and sits where they can see one shared phone or screen.
Status Code Drinking Game
What it is: Every HTTP status code becomes a drinking rule - 2xx are gentle, 4xx sting, 5xx are catastrophic.
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
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.
Set the screen and agree the triggers
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.
Events that change the round
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.
Run the game while you watch
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.
Change the viewing format
Log Mode
On-Call Roulette
REST in Peace
Cache Rules Everything Around Me
Sober Status
Balance watching and playing
How this screen game developed
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.
Status Code Drinking Game FAQ
What is the status code drinking game?
Do I need to know programming to play?
What does 404 mean in the game?
How do we play with real logs safely?
Can we play without alcohol?
By BestDrinkingGame.net Editorial Team · Published · Last updated