The Asia Cup T20 Super 4 clash between India and Sri Lanka in Dubai turned into a dramatic contest, ending in a tie after both teams posted identical totals of 202 runs for 5 wickets in their 20 overs. The match was eventually decided in a Super Over, but controversy struck when a Sri Lankan batter appeared to be run out yet was still declared safe due to technicalities in the umpire’s call.

A High-Scoring Thriller

Batting first, India put up a strong total of 202/5 with aggressive performances from their top order. Sri Lanka responded with equal determination, matching the score exactly at 202/5, forcing the game into a nail-biting Super Over.

Drama in the Super Over

Sri Lanka batted first in the Super Over. Kusal Perera was dismissed early for zero, giving India a psychological edge.

Then came the moment that sparked confusion: Sri Lankan captain Dasun Shanaka faced a delivery from Arshdeep Singh, missed the ball, and attempted a run. The wicketkeeper quickly threw the ball at the stumps, appearing to catch Shanaka out of his crease — a situation that usually results in a straightforward run out.

However, Arshdeep and India appealed for a caught-behind dismissal, believing the ball had touched Shanaka’s bat before reaching the keeper. The on-field umpire upheld the appeal and gave Shanaka out for a catch.

The Review That Changed Everything

Shanaka immediately went for a DRS review. Replays confirmed that the ball had not touched the bat, overturning the caught-behind decision.

But here’s where things got complicated:

• The appeal and on-field decision were only for the catch.
• Because the umpire had not ruled or referred the incident as a run-out, that mode of dismissal was not reviewed.

As a result, Shanaka was declared not out, escaping what looked like a certain run-out. This ruling baffled fans, who felt that common sense dictated the batter should have been dismissed anyway.

India Clinch the Win

Despite the confusion, Sri Lanka only managed to score 2 runs in the Super Over. India, needing just 3 runs, comfortably chased the target to secure victory.

Why Was Shanaka Not Run Out?

The explanation lies in cricket’s appeals and umpiring protocol:

• A batter can only be dismissed if there is a valid appeal for a specific mode of dismissal.
• In this case, the appeal was strictly for a catch, not a run-out.
• Once the review overturned the caught-behind, there was no active run-out decision on the field, leaving Shanaka safe.

This incident highlights a grey area in cricket’s decision-making system, where technicalities can override what appears obvious to spectators.

Fans and Experts React

The unusual outcome sparked debate among fans and analysts on social media. Some argued that the third umpire should have intervened to check for a run-out, while others defended the rules, pointing out that cricket’s laws strictly tie decisions to appeals made by the fielding side and the umpire’s original ruling.

Many fans compared the incident to previous controversial decisions in international cricket, once again raising questions about whether the Decision Review System (DRS) should allow umpires greater flexibility to rule on all possible dismissals in such scenarios.

Conclusion

The India vs Sri Lanka clash was already memorable for its tied scoreline, but the umpiring twist in the Super Over added another layer of drama. While India went on to win comfortably, the Shanaka non-dismissal is likely to be remembered as one of the more confusing moments of this year’s Asia Cup.

It also serves as a reminder that cricket is not only a game of skill but also of rules, appeals, and split-second judgments — sometimes leaving players and fans equally bewildered.