Twenty-four hours is a long time to trust a race server. Le Mans Ultimate’s endurance weekend has attracted a record crowd, giving its online racing technology a particularly public examination: can the software keep up with the commitment it asks of its drivers?
Traxion reported on 24 October 2026 that SteamDB recorded 11,941 concurrent players at around 5pm BST that Saturday, a new high for the game. That figure measures people playing through Steam simultaneously. It isn’t a count of entrants in one race, a sales total or a measure of how many drivers finished without problems.
The distinction matters because the encouraging attendance sits alongside a much more demanding question about endurance reliability. A busy server list looks good. Keeping a team’s entire day of racing intact is the achievement that actually earns trust.
A substantial grid, and a substantial commitment
Studio 397’s official event schedule specifies two separate starts: 11:00 UTC on 23 October and 13:30 UTC on 24 October. The second race is therefore scheduled to run into Sunday afternoon; at the time of writing, it has not reached its scheduled finish.
The event uses Le Mans’ WEC layout, Hypercar, WEC LMP2 and LMGT3 machinery, and 62-car splits. Open setups and disabled tyre warmers add to the preparation required. These are circumstances in which traffic, changing conditions and team organisation are part of the attraction, rather than background decoration.
For players, the scale creates a different sort of investment from a short online sprint. Preparation and shared driving time build a story long before the chequered flag. A technical failure late in that story doesn’t simply cost a few minutes. It can wipe out the reason a group rearranged its weekend.
The networking backdrop
This weekend follows an acknowledged period of networking trouble. In its 11 September community update, Studio 397 said it had rolled back some changes introduced since version 1.4 and was investigating further problems.
The studio then identified a suspected cause of phantom-collision behaviour and outlined public network tests building towards October’s Le Mans event. Its stated aim was to gather real-world data while monitoring changes live. Those were the developer’s expectations and plans, rather than a retrospective declaration that every issue had been eliminated.
Live testing has an understandable logic: large, long events expose combinations of conditions that are difficult to reproduce internally. It also asks something significant of paying players. Transparency about what is being tested, and what participants should report, becomes part of the service they are receiving.
Success cannot be read from one number
Traxion’s Saturday report described encouraging early stability but also brake failures in Friday’s running; it said brake wear had been disabled for Saturday. It also reported a driver-notification issue affecting 260 players that was resolved early in the race. Those are attributed observations from its report, not our own race experience or a completed official incident review.
The reported brake intervention is especially consequential. Endurance racing depends on managing machinery, but that management needs information players can act on. A simulated failure is a satisfying consequence when it follows an understandable decision; an unexpected failure without adequate feedback can feel arbitrary.
Disabling a system during an event may protect participation while sacrificing part of the intended simulation. That is an awkward compromise, and one worth explaining clearly once the full weekend has been assessed.
Practical details for participants
The official schedule asks drivers to enable +tracerudp=2 and send networking logs with any support ticket, including the event, date, time and timezone. It also urges owners of modest PCs to test large grids, weather and the full day–night cycle in single player before entering.
That preparation advice is useful because a circuit that runs comfortably in a quiet daytime session isn’t necessarily representative of the whole event. Reducing graphics settings may be a sensible trade if it keeps a long stint consistent.
The crowd is an encouraging sign of interest. The more meaningful verdict will come from completed races, documented failures and what Studio 397 changes in response. For an endurance sim, reliability is part of the driving experience: the finish line has to remain reachable after the players have done their part.