Rohit Sharma was dismissed in controversial fashion during Mumbai Indians' Indian Premier League (IPL) game against Kolkata Knight Riders (KKR) on Monday, with a lot of fans hitting out against the third-umpire and the use of UltraEdge technology.
Chasing a target of 166, MI lost their skipper at the end of the first over as the skipper’s lean patch continued.
Tim Southee opened the bowling for KKR. In the last ball of the over, Southee seemed to have got the better of Rohit, with the ball goes past closer to the edge of Rohit’s bat, hitting the thigh pad en route to keeper Sheldon Jackson, who took a brilliant one-handed catch.
The on-field verdict was Not Out but Sheldon wanted to take the review, and asked Shreyas Iyer for it, with KKR eventually opting for the DRS.
TV replays showed that there was spike on UltraEdge at the time when the ball was close to Rohit’s bat.
However, to the shock of MI team and supporters alike, there was a spike in UltraEdge even before the ball came in contact with Rohit Sharma’s bat. Bruce Oxenford, the third umpire, signalled to the on-field umpire to change his decision and a dejected Rohit who could hardly believe his dismissal was given out.
Some cricket fans condemned the poor umpiring standards in this IPL, with one of them even suggesting the use of Hotspot:
Importance of Hotspot is increasing day by day, use maximum technology and reduce the error.
— Johns. (@CricCrazyJohns) May 9, 2022
When the worlds most cash rich cricket league can't afford a hotspot technology.
Forget about on field umpires third empires are being the worst this season.
Why only #RohitSharma always😪 pic.twitter.com/7LiS7ZRXIV
— Rohit Chilakala (@RohitChilakala) May 9, 2022
Dear @BCCI @IPL Please get some good pairs of umpire who can hear and see properly! This type of bad umpiring it's just wasting the hardwork and dedication of all the players this stuff will happen someday in IPL final or the last ball of a deciding match. #IPL2022 #RohitSharma pic.twitter.com/jrU12xW3Ni
— Pu11 (@BTechnicalbiswa) May 9, 2022
Clearly a technical glitch. Spike popped up before the ball reached Rohit's bat. Important for the third umpire to keep the eyes open. #IPL2022 #MIvKKR pic.twitter.com/hfsfMvPb1m
— Subhayan Chakraborty (@CricSubhayan) May 9, 2022
How can the third umpire not see what we saw? Rohit was NOT OUT #MIvsKKR pic.twitter.com/UbbUH2BVcc
— Vikrant Gupta (@vikrantgupta73) May 9, 2022
from Firstpost Firstcricketnews Latest News https://ift.tt/efRId4t
Posted in Labels: Firstpost Firstcricketnews Latest News
