Twitter Reaction
Ajinkya Rahane Got Three Lifelines In The First Over Itself
By CricShots - Apr 10, 2022 7:33 pm
Views 14.3K

AIn cricket, umpires have often been seen getting criticized when they make wrong decisions that could potentially harm the game but with DRS all that has changed. During the Indian Premier League (IPL) 2022 match between Delhi Capitals (DC) and Kolkata Knight Riders (KKR), the on-field umpire gave Ajinkya Rahane out twice in the first couple of deliveries, and both times his decision got changed.

Ajinkya Rahane
Ajinkya Rahane was saved by the DRS

Delhi Capitals (DC) were at their ferocious best against Kolkata Knight Riders (KKR) in the first half of the game as they managed to post 215/5 after batting first at the Brabourne stadium in Mumbai. KKR opening batters came out after the innings break as they look to chase down the huge total as they look to remain on the top of the points table in IPL 2022.

WATCH – Varun Chakravarthy Cleaned Up Prithvi Shaw With The Googly

However, a funny incident took place on the first two balls of KKR’s innings. KKR’s opening batter Ajinkya Rahane was on-strike against Mustafizur Rehman when there was an appeal for caught behind and the on-field umpire gave him out.

However, Rahane went for the DRS straightaway and replays showed that the ball had touched his pad and not the bat. The decision was reversed by the third umpire. On the very next ball, Mustafizur appealed for LBW against Rahane and the on-field umpire again adjudged him out.

ALSO READ: Aakash Chopra comments on CSK’s recent performance in IPL 2022

It was a repeat of what happened in the previous delivery and Ajinkya Rahane reviewed it again. This time it showed that the KKR opener had edged the ball and then it hit his pad. Two DRS in two balls and both reversed by the TV umpire left the internet amused. However, on the third ball, Rahane and nicked teh ball and the keeper had caught ball but no one appealed.

Here is the video of the overturned umpiring decisions:

 

Here is how the fans reacted to the incident:

×