Two controversies in two days have put IPL 2026’s officiating under a microscope — and Wednesday’s GT vs DC match at Arun Jaitley Stadium has sparked the wider debate about whether a 150-year-old law has any place in a sport that now has a third umpire and ultra-edge technology at its disposal.

The Match That Broke in the Final Two Balls

Gujarat Titans posted 210/4 in a batting masterclass — Shubman Gill making 70 on return from injury, Jos Buttler contributing 52 and Washington Sundar a composed 55 to set Delhi an imposing target after GT’s winless start to the season.

Delhi Capitals’ reply was shaped almost entirely by one man. KL Rahul — batting at a strike rate approaching 177 — made 92 off 52 balls in one of the finest individual chases of IPL 2026. Pathum Nissanka added 41, and David Miller carried DC to the final over needing 13 off six balls.

Prasidh Krishna — the man with the ball — conceded boundaries off the first four deliveries. With 2 needed off 2 balls, David Miller faced the fifth delivery, decided against taking a single, and played for the boundary. He missed.

The final ball: Kuldeep Yadav on strike, two needed, one ball. He swung and missed. As the ball reached Buttler behind the stumps, Kuldeep set off for a desperate bye. Buttler — who had waited all evening for this moment — gathered cleanly, pirouetted and sent a flat, direct throw to the bowler’s end that shattered the stumps before Kuldeep could ground his bat. GT won by one run, their first win of IPL 2026.

The Delivery That Social Media Is Still Arguing About

But the final ball was not the only decisive moment of the evening. At the 9.2 over mark — midway through the DC chase — a Rashid Khan delivery struck Nitish Rana on the pads. The on-field umpire raised his finger, calling lbw. But Rana and his partner had already completed a single before the decision was given — running from the non-striker’s end as Rana walked off.

DC went upstairs for the review. DRS showed Rashid’s delivery was missing leg stump — Rana was not out. The on-field decision was overturned. Good news for DC. Except for one thing: the run they had taken did not count.

DC completed their innings on 209. GT won by one run. The run that was wiped by the dead ball rule was, mathematically, the margin of defeat.

The Law Behind the Controversy

This is not an umpiring error. It is the law operating exactly as written — and that is what has made the debate so heated.

MCC Law 20.1.1.3 states:

“A ball is considered dead after a batter is dismissed. The ball will be deemed to be dead from the instant of the incident causing the dismissal.”

Law 20.6 goes further:

“Once the ball is dead, no revoking of any decision can bring the ball back into play for that delivery.”

In plain terms: the moment the umpire raised his finger and called Rana out — even though that decision was later reversed — the ball became dead. Everything that happened from that moment forward, including the run the batters completed, was nullified. The DRS reversal cleared Rana of the wicket but could not undo the dead ball.

The Case For and Against the Law

The law exists for legitimate reasons. If a dismissed batter could still benefit from runs scored after the wicket fell, it would create impossible situations — batters might manufacture dismissal appeals to steal runs, or there would be chaos around which completed actions count and which don’t. The law draws a clean line.

The counter-argument is equally compelling. If the umpire’s on-field error — not the batting team’s mistake — is what triggered the dead ball, then a team is being penalised for an incorrect decision that was later rectified. The DRS exists precisely to correct umpiring errors. If the correction cannot include restoring the run scored, then the DRS has only partially undone the damage the error caused.

Social media reactions were pointed.

“Nitish Rana completed a single, but the run wasn’t counted because the umpire had initially given him out, even though DRS later overturned the decision in his favour. DC eventually lost the game by 1 run. That foolish rule need to go out — it costed Delhi the match.”

R Ashwin was tagged in a post highlighting the incident, with fans directly asking him to weigh in on whether the rule was fair.

A Season Full of Questions for the Officials

This is now the third significant officiating controversy of IPL 2026 in the space of a fortnight — after the ball-change penalty awarded to Lahore Qalandars’ Fakhar Zaman in the PSL, the dubious boundary catch in the KKR vs LSG match on Thursday, and now this dead ball ruling. In each case, the laws were technically applied correctly — but each case has exposed a gap between what the law says and what most people watching believe justice looks like.

The question of whether Law 20.6 should be amended — specifically in scenarios where the dead ball was triggered by an umpiring error that DRS later reversed — is now firmly on the table.