A Formula 1 race was delayed by a software bug on Sunday, and the fix was a patch written and deployed during the red flag that the bug itself had caused. The start of the Bahrain Grand Prix, run at a wet Sepang circuit, was aborted after a large number of cars suffered a power-unit software glitch. It was the first wet race for the 2026 generation of cars, and the bug lived in exactly the mode that rain brings out: when drivers were crawling at very low speeds, the power-unit controller’s wet-weather state dropped them into idle and left them there. Several cars got stuck in that loop partway through the two planned formation laps, which is the worst possible place to stop - the grid was already forming, the track was already live, and the whole field could do nothing but sit.
The repair was improvised in real time. With cars stranded, the FIA had to code a software patch for all eleven teams and have it installed during the following red-flag stoppage, lifting the usual wet-weather power reduction in the affected zones. The race finally started fifty minutes late. Lando Norris, whose Mercedes-powered car was among those hit, called it “just horrible” and said the weekend proved Formula 1 “shouldn’t have any of that stuff, the electronic side.” Oscar Piastri was drier about it: “I’ve never seen an F1 race delayed by a bug. That was a new one.” When the turbo quits, he added, “you might as well push the car instead of using an engine.”
🎩 Cask’s Take
The reason every affected car failed at the same moment is that Formula 1 does not let each team write its own throttle logic. The FIA ships a single spec control system precisely so that teams cannot sneak traction control back in - a driver aid long banned because it blunts the skill the sport is selling. That is a sound goal, and it carries a cost the sport just paid in front of a global audience: when you centralize control to guarantee fairness, you also centralize failure. One bug stops being one team’s bad afternoon. It becomes everyone’s, at once, on the one lap where the whole field is bunched together.
What struck me is how ordinary the recovery looked. A bug report, an emergency patch, a forced rollout to every operator mid-incident. That is an outage postmortem happening at two hundred miles an hour. Formula 1 has spent a decade importing software into a sport built on mechanical certainty, and this weekend it inherited software’s oldest failure mode: the shared dependency, the single point of failure, the bug that takes the entire fleet down at once.
Norris’s instinct is to rip the electronics out. But the electronics are what keep the drivers in charge. The traction-control ban is enforced by software, the wet-weather power curve is software, the energy management that makes these cars hybrids at all is software. You cannot keep the fair racing and throw away the machine that enforces it. You can only decide how much of the race you are willing to let a computer hold, and then live with the fact that computers fail.
Piastri’s line is the one to keep. “I’ve never seen an F1 race delayed by a bug.” Give it a few years and nobody will find that strange at all.