Player concurrency
Player concurrency (also called concurrent players or CCU — concurrent users) is the number of players connected to game servers at the same time. It’s the primary metric that determines how much infrastructure capacity a multiplayer game needs at any given moment.
Peak vs average concurrency
Peak concurrency is the highest number of simultaneous players, typically occurring during evening hours in the game’s largest region, during launches, or during events. Average concurrency is the typical load across a full day.
The ratio between peak and average matters for infrastructure planning. Most games see a peak-to-average ratio of 2x-5x. A game averaging 10,000 CCU might peak at 30,000-50,000. Provisioning infrastructure for peak wastes money during off-peak hours. Provisioning for average means players can’t connect during peaks.
From concurrency to server count
To calculate required servers: divide concurrent players by players per session. A game with 10,000 CCU and 10 players per match needs approximately 1,000 active server containers. Each container requires a specific vCPU and memory profile depending on the game’s tick rate and simulation complexity.
Common CCU milestones
- 100 CCU — Early access, closed beta. A handful of servers.
- 1,000 CCU — Small live game. 50-200 servers depending on match size.
- 10,000 CCU — Healthy indie or mid-tier game. Infrastructure costs become material.
- 100,000 CCU — Major title. Multi-region deployment essential. Cloud bursting needed for peaks.
- 250,000+ CCU — AAA launch. Requires proven infrastructure with automatic scaling and multi-provider failover.