Le Mans Ultimate revises large-scale Le Mans test race plan
The February 2026 community update says larger team-race testing has been scaled back after server issues appeared with 130+ connected clients. The next Le Mans test is now a single 12-hour, 62-car race on Friday 27 February, with a possible second run on Saturday if the first test is successful.
We’ve got a scheduling and operations update from Le Mans Ultimate’s latest community post. The studio says recent 38-car endurance races have run well, but larger team-race scenarios exposed server-side issues at much higher connection counts.
What changed
Cars
- No car content changes were announced.
Multiplayer / online events
- The team identified “unacceptable service issues” when running events with 130+ clients connected to servers.
- These problems were found during automated testing tied to preparation for a larger Le Mans test race.
- The issue is described as anomalies in network traffic within containers on high-load servers.
- Because of this, the planned approach for larger team races is changing.
Events / scheduling
- The revised Le Mans test plan is now one race on Friday 27 February.
- Format for that test:
- 12-hour race
- Full day/night cycle
- 2x time scale
- 62-car grid
- Le Mans
- Single timeslot starting at 10:00 UTC
- The limited single-slot format is intended to let the developers and community closely monitor server behaviour.
- If the Friday test goes well, the team plans to run another race with the same format on Saturday 28 February.
- Any future 24-hour test race will only be scheduled after reviewing these tests and deciding whether more follow-up testing is needed.
For league ops, we should treat this as a capacity-and-schedule change: notify entrants, avoid locking in 24-hour plans yet, and be ready to adjust around the Friday test outcome.
From the changelog
Structured change list parsed from the official notes.
cars
- Hi everyone, First of all, thank you for the continued support and turnout for our endurance events in Le Mans Ultimate. Our recent 38-car 4, 6 and 8 hour races have been running consistently well, and we’re really pleased with how those events have performed. However, as we continue to gear up for much larger team races, we’ve identified some unacceptable service issues when running events with 130+ clients connected to servers - which is expected for longer races and 62 car grids like Le Mans. These issues don’t show up in smaller races but become critical at this scale. Because of this, we’ve made the decision to change how our larger team races will run going forward. [h3]Why the change?[/h3] In our automated testing after completing some work to prepare for the upcoming test race, we found some anomalies with the network traffic within containers on these high-load servers. This led us to need to explore new options to handle this type of event. However, it won’t be possible to run the level of testing required to give us enough confidence to run several 24 hour races concurrently next weekend. We know many of you have set aside that weekend for racing and already made plans, so to try and make sure you still get track time the test will still go ahead but with following changes, [h3]Revised Test Plan for Le Mans[/h3] To properly validate the new setup, we will now run a test race initially on Friday 27th February only : [*] 12-hour race with full day/night cycle (2x time scale) [/*][*] 62 car grid [/*][*] Le Mans [/*][*] Single timeslot with start time: 10:00 UTC (Friday 27th February) [/*] This limited time slot will allow our community and development team the ability to monitor closely the behaviour in “the wild”. [h3]What happens next?[/h3] [*] If Friday’s test goes well, we’ll proceed with another race with the same format on Saturday 28th February - we will communicate this around the finish of the Friday race. [/*][*] Once the test races are reviewed, we will pragmatically analyse them and schedule any follow-up tests if required before committing to the next 24 hour test race. [/*] We know changes like this aren’t ideal and will be disappointing for some, but our priority is to deliver stable, enjoyable racing, rather than push ahead and potentially cause the community the disappointment in losing time towards testing if we are not as confident as we could be with more time. Thank you everyone for your understanding, flexibility, and continued passion and we will share further updates as soon as we’ve reviewed the results from the Friday test. Until then enjoy getting those liveries ready and let the practice laps begin! See you on track 🏁
Official sources
Running a Le Mans Ultimate league?
Racey automates signups, stewarding & standings — so you run the racing, not the spreadsheets.
Get started free →More Le Mans Ultimate updates
Le Mans Ultimate 1.3.3.4 patch fixes engineer-mode settings after driver swaps
This hotfix addresses a driver-swap issue where engineer mode changes could revert to pre-pitstop values after handing the car to a teammate.
Le Mans Ultimate 1.3.3.3 patch released
This hotfix updates Le Mans Ultimate to Build ID 23631476 and fixes an occasional dead-state lock when a practice server closes.
Le Mans Ultimate 1.3.3.2 patch update
This hotfix addresses a DLC unlock issue, a pit stop release bug tied to brake duct changes, Circuit de la Sarthe visual and anti-cut fixes, a small BOP adjustment for several cars, and specific BMW and Ford LMGT3 fixes.