The 7 DRS Calls That Aged Badly — IPL 2026 Mid-Season Controversy Ranker

Every IPL season has its DRS flashpoints. Umpires' call turning a plumb leg-before into a not-out. A ghost edge that UltraEdge couldn't confirm. A run-out referral where the TV umpire spent 90 seconds on a single angle. IPL 2026 has already delivered a few that aged terribly — and cricket Twitter refuses to let them die.

This is the mid-season controversy ranker. Seven DRS calls from IPL 2026 ranked by how wrong they looked on replay, which team they hurt, and how loud the internet got. (Quick caveat: we're ranking reaction intensity and replay optics, not overruling the letter of the playing conditions.)

How the ranking works

Each DRS call gets scored on three axes:

• Replay optics (1-10) — how wrong it looked on slow-motion
• Match impact (1-10) — how much the call changed the game
• Twitter heat (1-10) — how big the reaction was on X and Cricbuzz comments

Total out of 30. Let's count down from #7.

#7 — The "ball-tracking froze" moment (CSK vs MI, Match 11)

A plumb-looking lbw shout against a CSK middle-order batter was initially given out. On review, ball-tracking briefly stalled on the broadcast and came back showing clipping leg stump, converting "out" on field into "umpire's call".

• Replay optics: 6/10 (ball-tracking hesitation is always suspicious)
• Match impact: 5/10 (CSK eventually lost by a narrow margin)
• Twitter heat: 4/10
• Total: 15/30

The TV feed froze for close to 3 seconds mid-review. That was the controversy — not the call itself. Broadcasters later confirmed a rendering glitch.

#6 — The sharp-spike UltraEdge vs LSG (Match 14)

An LSG batter walked off after UltraEdge showed a spike, but replay suggested the spike coincided with bat hitting pad, not ball touching bat. Pant's visible annoyance on the boundary turned into a mini press-conference controversy.

• Replay optics: 7/10
• Match impact: 6/10 (LSG chase lost momentum)
• Twitter heat: 6/10
• Total: 19/30

The bigger issue was TV umpire process — he didn't ask for a second angle before confirming. BCCI match referee later said the decision was "correct under the protocol" but the optics were ugly.

#5 — The no-ball that never was (SRH vs KKR, Match 16)

An SRH bowler's front foot looked clearly past the popping crease on a wicket delivery. The third umpire was meant to check automatically under the current protocol. He checked and ruled "legal delivery". Freeze-frames on social media showed the toe appearing to hang over.

• Replay optics: 7/10
• Match impact: 7/10 (the wicket was a top-order dismissal)
• Twitter heat: 7/10
• Total: 21/30

KKR fans spent two days posting the freeze-frame. The ICC's guidance says "some part of the foot behind the line" is legal — and that's what the third umpire saw. Technically correct. Visually painful.

#4 — The Shreyas Iyer stumping controversy (PBKS vs RR, Match 19)

Shreyas Iyer was given out stumped off a Jadeja delivery when the Rajasthan keeper broke the stumps with gloves that appeared to dislodge the bails before the ball arrived. The third umpire used only one side-on angle and one straight-on angle — no zoomed frame-by-frame.

• Replay optics: 8/10
• Match impact: 8/10 (PBKS captain walked back for a well-set 40)
• Twitter heat: 7/10
• Total: 23/30

This one hurt PBKS — Shreyas Iyer was anchoring a chase. The Jadeja-to-RR narrative arc added fuel. Rajasthan defended their position, but replays kept trending for 48 hours.

#3 — The "soft signal" that split Twitter (GT vs DC, Match 20)

A low catch at deep cover was sent upstairs with a soft signal of "out". The third umpire found no conclusive evidence the ball had bounced before the fielder's hands. Soft signal stood. The batter walked.

• Replay optics: 8/10 (side-on angle was genuinely ambiguous)
• Match impact: 9/10 (GT lost the match by a narrow chase margin; Buttler was the batter)
• Twitter heat: 8/10
• Total: 25/30

This one reopened the entire "scrap the soft signal" debate that ESPNcricinfo has been running for years. Jos Buttler (at GT this season) made clear on the post-match interview that he "didn't feel it was out, but respected the process". Twitter was less polite.

#2 — The Maxwell umpire's call (PBKS vs MI, Match 13)

Glenn Maxwell (now at PBKS) was trapped leg-before on what ball-tracking showed as half the ball hitting middle and leg. The on-field decision was not out. MI reviewed. Ball-tracking returned "umpire's call". Not out stood. Maxwell went on to score a match-winning 65 off 38.

• Replay optics: 9/10 (looked clean out on replay)
• Match impact: 10/10 (single-handedly changed the result)
• Twitter heat: 8/10
• Total: 27/30

The "umpire's call" debate is the most contentious DRS question in cricket. Ball-tracking said half the ball was hitting the stumps, the on-field call was not out, so the call stayed. That's the protocol. Mumbai fans still haven't forgiven it.

#1 — The Samson "ghost edge" controversy (CSK vs RCB, Match 15)

The call that defined the first half of IPL 2026. Sanju Samson, batting on 40s, chased a wide Siraj delivery. On-field call: not out. RCB reviewed. UltraEdge showed a clear spike as ball passed the bat — but the ball was visibly past the bat at that point on the side-on angle. Third umpire ruled not out. Samson went on to score a match-winning 115*.

• Replay optics: 9/10 (spike location was suspicious)
• Match impact: 10/10 (CSK's first win of the season)
• Twitter heat: 10/10
• Total: 29/30

The spike vs bat-timing question is the trickiest DRS puzzle. On the side-on angle, the ball looked past the bat when the spike appeared — meaning the spike was likely bat-on-pad, not ball-on-bat. Third umpire played it safe with "no conclusive evidence" (the benefit-of-doubt protocol). RCB fans were furious. Cricbuzz ran post-match analysis pieces for three days.

The pattern emerging

Look at the top three. They have one thing in common: close ball-vs-bat timing where two frames of footage can flip the verdict.

The IPL could genuinely consider:

• Two side-on cameras at 60fps minimum (current is 50fps on some broadcasts)
• Mandatory zoomed frame-by-frame on soft-signal catches
• Audio sync verification — UltraEdge vs visual pass often mismatches by 1-2 frames

Until any of that happens, expect IPL 2026's second half to add another three or four entries to this list.

FAQ

Q: What is "umpire's call" in DRS?
A: When ball-tracking shows less than half the ball hitting the stumps on an lbw, the original on-field decision stands. It's meant to preserve umpire authority on marginal calls, but it's the most controversial part of DRS.

Q: Why can't UltraEdge be 100% accurate?
A: UltraEdge relies on the stump mic picking up the sound of contact. Bat hitting pad, pad hitting bat, or even the handle rattling can produce a spike. The third umpire has to judge whether the spike timing aligns with ball passing bat on the visual.

Q: Can a team appeal an umpiring decision in the IPL?
A: Not formally. Teams can privately raise concerns through the match referee, but there's no retrospective overturning of on-field decisions once the match ends.

Q: How many DRS reviews does each team get per innings in IPL 2026?
A: Two unsuccessful reviews per innings, with the review remaining if the outcome is "umpire's call". That's been the protocol since 2023.

Q: Why are IPL DRS decisions more controversial than international cricket?
A: Higher number of matches (74 in 2026), faster broadcast turnaround, and T20 format means each wicket is higher-leverage. Every edge or lbw can swing a title race.

Q: Will the BCCI review DRS protocols after IPL 2026?
A: Possible. BCCI's technical committee typically reviews match-officiating after each season. The "umpire's call" debate keeps coming up but hasn't produced a protocol change yet.

Keep reading

• IPL 2026 Umpire Accuracy Data Ranker
• DRS Rules Explained — How Reviews Actually Work
• IPL 2026 Match 15 Recap — Samson 115* Shocks RCB
• The Soft Signal Debate — Why T20 Needs a Rethink
• IPL 2026 Fielding Efforts Leaderboard — Top 10 Moments