Understanding the Software Glitch That Caused F1 Chaos in Malaysia
Unraveling the Technical Mystery Behind the Malaysian F1 Race Disruption
Unforeseen Power Loss During Formation Laps
The commencement of the inaugural wet-weather Grand Prix of the 2026 Formula 1 season was plunged into disarray. Max Verstappen, leading the pack, experienced a sudden power reduction during the safety car formation laps, an issue that subsequently affected Lewis Hamilton and numerous other competitors.
Race Interruption and the FIA's Swift Response
Officials were compelled to red-flag the race, leading to a 40-minute postponement before the competition could resume. Nikolas Tombazis, the FIA's single-seater director, later confirmed to the press, including Motorsport.com, that the disruption was caused by a software defect within the system collaboratively developed by the FIA and participating teams over several years.
“We weren't able to thoroughly test the software as much as we desired due to the limited wet-weather running this season. A confluence of factors led to this bug manifesting,” Tombazis elaborated in a post-race media briefing. “Essentially, during the formation lap, some vehicles slowed down significantly, nearly coming to a halt. A compounding effect between cars meant some almost stopped entirely. This bug then prevented power from being reinstated, leaving the cars unable to move.” This issue is directly linked to the regulated reduction of electrical power to 250kW under wet conditions.
Untested Scenarios: The Root Cause of the Glitch
Despite testing by various teams, including Red Bull and Racing Bulls, the software was not evaluated under safety car conditions at such unusually low speeds. At the Sepang International Circuit, these minimal speeds were inadvertently reached in specific sectors, triggering the described malfunctions.
Drivers' Bewilderment and the Technical Explanation
In practical terms, drivers reported a complete lack of throttle response, a sensation Oliver Bearman of Haas described as alarming. “I’d never encountered or felt anything like it. I was astonished that… I wasn’t even aware the FIA could intervene with our throttle pedal. It was quite frightening, honestly,” he stated.
“My accelerator simply ceased functioning. It felt disconnected, with the engine merely idling. It was profoundly strange, truly shocking.” A pertinent question arose regarding the impact on the internal combustion engine, which ideally should remain unaffected at low speeds. The FIA lacks a definitive answer but suggests the bug channeled all throttle input towards recharging the MGU-K, explaining the perceived unresponsiveness.
Initially, Mercedes-powered cars appeared less affected, but Tombazis clarified this was coincidental, attributing it to the varying speeds experienced in different mini-sectors. “Not all cars achieved the same low speeds during the formation lap. There was a sort of accordion effect. Max, being at the front, slowed considerably, and then some cars braked more sharply due to surprise. This led to some cars experiencing the problem while others did not.”
Emergency Solution: A Rapid Software Patch
The FIA was then tasked with swiftly enabling the race near Kuala Lumpur to proceed. Tombazis explained to Motorsport.com: “Fortunately, our technicians identified the problem very, very quickly. The update was executed with great competence, despite being a rushed effort. The priority was to restart the race as promptly as possible, so the reaction time was quite impressive.”
“It wasn't an ideal solution, and naturally, the updates were not fully tested, but I believe it was the correct way to manage such a situation.” Essentially, the update involved the FIA temporarily overriding the energy limit constraints related to the 250kW power cap in the specific mini-sectors where the bug had occurred. While not a permanent fix, it served as an emergency measure to ensure the race's continuation.
“In some sectors, certain power reductions were circumvented,” Tombazis confirmed. “Clearly, we didn't have several days for these updates; we had mere minutes. But fortunately, I believe we managed it without compromising safety, fair racing, or integrity.”
Post-Mortem: Lessons Learned and Future Safeguards
Following the FIA’s update, all teams were required to install the modified software, accounting for the delay before the restart. Although the Bahrain Grand Prix in Malaysia was salvaged, it raises questions about how the FIA overlooked this issue during extensive preparations and why it only emerged in the sixteenth round of the championship.
“The software underwent testing, but not under these specific circumstances,” Tombazis responded. “What caught us off guard was the exceptionally low speeds attained by the cars, which had not been accounted for in normal testing protocols.”
During tire tests, where the software was evaluated, such extremely low speeds were not reached, which is understandable. However, a significant counter-argument is that in rainy conditions, the deployment of a safety car and subsequent low speeds are highly probable. Should the FIA have foreseen this, and was this the organization’s most critical oversight?
When questioned by Motorsport.com, Tombazis acknowledged: “Any bug signifies an error. I don't know of any software without bugs and requiring updates. Your computer likely updates every three days, and those are all fixes for bugs.”
“Naturally, one hopes to anticipate these scenarios, but sometimes a unique combination of events is not properly foreseen, leading to problems. I believe if we had conducted more comprehensive testing, we would likely have identified it in advance and avoided such a situation.” While the cause is now understood and a temporary solution implemented, the FIA faces further internal scrutiny to prevent similar incidents. “We all wish it were simpler, but with so much electrical energy involved, it becomes more complex. The race concluded about an hour ago, and we haven't conducted a full debrief to determine how to avert such issues.”
“After every race, we conduct a thorough debrief to pinpoint critical areas. This was undeniably a major critical point, and we must ensure it doesn't recur. But can I guarantee this specific problem will never happen again? Yes. A problem in general, no. However, we will certainly endeavor to prevent it.