Finn Allen Boundary-Catch Controversy — KKR vs LSG, IPL 2026

The boundary-rope catch has become one of the most contested mechanics in T20 cricket. The Laws are unambiguous: a fielder must be inside the boundary at the moment of catch completion and at all subsequent moments while in contact with the ball. Even momentary contact with the rope renders the boundary scored, not the catch taken. The difficulty is procedural: at high speed, with sliding fielders and a flexible rope that bunches and re-flattens with movement, the on-field umpire often cannot see what the broadcast cameras can.

The IPL has progressively expanded the use of the third umpire on boundary catches. Soft signals from on-field umpires were reformed in 2023 after a series of controversial overturns, and from 2024 onwards the standard expectation has been that any catch in the vicinity of the rope is referred upstairs as a matter of course, regardless of how clean it appears live. The Allen dismissal turned on this expectation. The on-field umpire's decision to give out without referral was, in form, a return to a pre-2024 norm — and it produced exactly the controversy the new protocol had been designed to prevent.

Lucknow Super Giants entered the match in indifferent form. Digvesh Rathi, the wrist-spinner who took the catch, had been one of LSG's success stories of the season and was fielding at deep third under a clear plan to attack Allen, who had been targeting that area in the powerplay across the tournament.

KKR were chasing 184 at Eden Gardens after a strong LSG batting effort. Allen, restored to the opening slot, walked out alongside Quinton de Kock with the home crowd expecting an aggressive start. Allen took a single off the first ball and faced LSG's seam-up bowler in the second over. He attempted to ramp a length ball over deep third, off the toe of the bat. The shot was high and short of the rope; Rathi, sprinting in from the boundary, judged the trajectory well, slid, and held the ball low.

The on-field umpire, looking up from square leg, indicated out within a fraction of a second. Allen, who had been running, paused mid-pitch to look at the big screen. The big-screen replay was inconclusive on first viewing — the camera angle suggested Rathi's foot had been in the air at the moment of catch — and Allen began the walk back. Within seconds, alternative replay angles from the boundary-line camera circulated on social media, and the broadcaster's commentary turned sceptical.

Allen, asked to set the tone in a steep KKR chase, attempted to clear deep third in only the second over of the innings. Rathi sprinted from the rope, slid, and held a tumbling catch. On-field umpire signalled out almost instantaneously and did not formally refer the take to the third umpire — a procedural step that has become standard for any boundary-edge catch in T20 cricket since the rope-touch dismissals of the late 2010s.

Within minutes, broadcast replays from the boundary-line camera showed Rathi's left boot apparently in contact with the rope as he completed the take. The TV umpire eventually reviewed the footage and ruled the dismissal fair, judging that Rathi's foot was on the playing side of the rope at the moment of catch completion. The decision did little to settle the controversy: Allen had already walked off, the over had been completed, and the question for KKR was procedural, not just outcome-based. Why had the catch not been referred immediately?

Captain Rovman Powell, speaking after KKR lost a tight chase, said publicly that the team was "frustrated" by how the decision had been handled. KKR's official statement called for boundary catches to be referred upstairs as a default. The incident reignited a debate that has run through every IPL since soft-signal protocols were tightened: at what point does a fielder's contact with the rope render a catch invalid, and who decides?

“We're frustrated. A catch that close to the rope should always go upstairs. That's the protocol everyone is supposed to be working under.”

“I knew my foot was inside. The TV umpire confirmed the catch — that's the end of it for me.”

“Boundary catches in proximity to the rope should default to a third-umpire referral, irrespective of the on-field umpire's confidence.”

KKR lost a tight chase, and Powell's post-match comments — measured but direct — became the dominant story of the night. By the following morning the BCCI had clarified its position: boundary catches in close proximity to the rope should default to a third-umpire referral, even where the on-field umpire is confident in their initial judgement. The clarification did not name Allen's dismissal but was widely understood to be a direct response to it.

The third umpire, KN Anantha Padmanabhan, drew criticism for the speed of his subsequent review — commentators noted that he had spent only seconds with each replay angle before confirming the catch, where the procedure typically calls for multiple angles to be considered before a final ruling on a marginal take. The BCCI did not formally censure Padmanabhan but quietly removed him from third-umpire duty for the next two KKR matches, a move not officially confirmed but widely reported in cricket media.

Digvesh Rathi himself defended the catch, saying he had been confident his foot was inside the rope, and pointed out — correctly — that the third umpire had ultimately upheld the decision. Allen declined to comment publicly. Lucknow Super Giants made no statement beyond confirming they had no intention of revisiting the dismissal.