Valve have reportedly hidden official Counter-Strike 2 servers from an API that was used to track activity across the game and estimate how many players were actually playing at a given moment. The change was revealed by CS2 dataminer aqua on his X account, while Valve have not publicly explained the decision.
OFFICIAL CS2 SERVERS CAN NO LONGER BE TRACKED
According to aqua, Valve official Counter-Strike servers have disappeared from the API that previously allowed him and other third parties to monitor active players on those servers.
Valve hid their own official @CounterStrike servers from the API that allowed us to track the real number of players actively playing the game at any moment.
I wonder why… https://t.co/30mKJEt2Zj pic.twitter.com/lELFIcStiI
— aqua (@aquaismissing) September 18, 2026
The change concerns server-level tracking rather than the standard public player count for Counter-Strike 2.
Steam provides infrastructure for retrieving information about game servers, including an ISteamMatchmakingServers interface used to access the Steam game server browser. Valve documentation also lists separate Steam Game Server APIs as part of Steamworks.
However, aqua did not specify the exact endpoint affected by the latest change, so it is currently unclear precisely what Valve changed on the technical side.
STEAM PLAYER COUNT IS STILL AVAILABLE
The overall Counter-Strike 2 concurrent player count has not disappeared.
Steam continues to provide a GetNumberOfCurrentPlayers method, which returns the number of users currently active in a Steam application. In other words, the public CS2 player counter can still be accessed separately from the official-server data discussed by aqua.
The difference is important. Steam concurrency shows how many accounts currently have CS2 active, while the server data described by aqua provided a way to estimate how many players were actually connected to Valve game servers at a particular moment.
Removing official servers from that tracking method therefore makes independent comparisons between overall CS2 concurrency and actual activity on Valve servers more difficult.
AQUA PREVIOUSLY TRACKED MAJOR CHANGES IN CS2 PLAYER ACTIVITY
This type of data has already been relevant in discussions surrounding bot farms in Counter-Strike 2.
In August 2026, aqua reported a major week-over-week decline in activity across several modes. According to data he shared at the time, Deathmatch lost around 18,000 players, Casual dropped by roughly 12,000, Arms Race by 5,000 and Retakes by approximately 2,500.
The drops coincided with reports of action against farming accounts and led to speculation about a new Valve ban wave. Valve did not publicly disclose the number of accounts banned or officially confirm that all of the decline was caused by bot removals.
That previous example shows why more detailed player-activity information can be useful beyond simply watching CS2 peak player numbers.
VALVE HAVE NOT EXPLAINED THE CHANGE
Valve have not announced the server-tracking change or provided a reason for restricting access as of publication.
aqua ended his post with “I wonder why…,” and the change has already sparked speculation about bots and the accuracy of CS2 player numbers. There is currently no evidence establishing that either of those issues was the reason for Valve decision.
For now, standard Steam concurrency remains publicly visible, while the method aqua says was capable of tracking players specifically through Valve official Counter-Strike servers can no longer provide the same data.
