IPL 2018: Despite Heroics, Jasprit Bumrah Faces Fans' Ire As Mumbai Indians Lose Another Last-Over Thriller
Jasprit Bumrah was smashed for 18 runs off the penultimate over of the match, leaving Rajasthan with 10 runs to get in the final over.
- Santosh Rao
- Updated: April 23, 2018 10:55 am IST
Highlights
-
Fans on Twitter troll Mumbai Indians pacer Jasprit Bumrah
-
Bumrah bowled a no-ball in the 19th over and gave away 18 runs
-
Mumbai lost to Rajasthan by three wickets
Jasprit Bumrah produced a brilliant 17th over that all but derailed Rajasthan Royals' chase against Mumbai Indians in an IPL 2018 match at the Sawai Mansingh Stadium in Jaipur on Sunday night. The right-arm pacer took two wickets and gave away just one run in his third over of the match that left the hosts needing 44 runs off the final three overs. However, Mumbai's hero soon turned villain as he was smashed for 18 runs off the penultimate over that brought Rajasthan back from the dead. Fans on Twitter were not amused, not because of the number of runs leaked by Bumrah but for the no-ball he bowled at a crucial juncture of the match. Rajasthan went on to win the match by three wickets and two balls to spare.
1. whoever told Jasprit Bumrah to focus on a hard length instead of yorkers in the death is a terrible coach
— Shalaj Lawania (@_Apex_Predator_) April 22, 2018
2. about time Bumrah gets a knock on his head for the consistent no-balls in high pressure situations
3. lol #RRvMI #IPL
Name : Jasprit Bumrah
— Hariharan Durairaj (@hari_durairaj) April 22, 2018
Hobby : Bowling NoBalls & Losing Games for his Team#RRvMI pic.twitter.com/GGL64314hT
For everyone else there's a stepping stone to success
— Simplicity (@SimplySimple_me) April 23, 2018
Jasprit Bumrah: oversteps the success & leaves it behind.
Cancelled Ola cab today as the driver's name was Jasprit Bumrah. Didn't want to take the risk of jumping signals.
— Abhinav karna (@abhinav_karna) April 22, 2018
Mandatory Bumrah No-ball under pressure.. This is unacceptable from a man of his abilities. Absolute crime #RRvMI
— The Lyrebird (@mechengg1101) April 22, 2018
Jaipur Traffic Police, why had you trolled Jasprit Bumrah ???
— A n u p a m (@Anupam183) April 22, 2018
Look, what a nice guy he is.
With the today's No-Ball, he has won the match for your Rajasthan Royals....
#RRvMI #IPL2018 https://t.co/CQL4LZ6hsM
Rajasthan royals needed 28 off 12 balls then no ball specialist jasprit bumrah gave away 18 runs in an over and won the game for opposite team but but world's best death bowler who wins the game single handedly for opposition#VIVOIPL#IPL2018#RRvMI pic.twitter.com/2LzJSIOFuq
— Ahsan Jaffri (@AhsanJaffri5) April 22, 2018
Jasprit Bumrah and NO Ball! Definitely a better love story than Romeo & Juliet!#RRvMI
— Avijit Maity (@AvijitMaity580) April 22, 2018
This is not the first time that Bumrah has bowled a no-ball that has ended up costing his team dear.Â
During the ICC Champions Trophy final on June 18, Bumrah got the better of Pakistan opener Fakhar Zaman, who edged a ball to Mahendra Singh Dhoni while batting on 3. The umpire checked for a no-ball and the replays showed that the bowler had overstepped his mark.
Zaman made full use of the opportunity as he went to score his maiden ODI century and was only dismissed after scoring 111 more runs. India lost the match by a massive 180-run margin.
On Sunday, Bumrah was again guilty of overstepping the mark. He was then hit for boundaries in the fourth and the final ball, leaving Rajasthan needing 10 off the final over.
Krishnappa Gowtham was the hero for Rajasthan as he blasted 33 not out off just 11 balls, including a six off the final over that got Rajasthan across the line with two balls to spare.
Incredibly, this was the fourth time that Mumbai have lost a last-over thriller this season. Their inability to close out matches means that they are now second from bottom, on same points as last-placed Delhi Daredevils.
After five matches, Mumbai have won just one match and will quickly need to regroup if they are to come even minutely close to defending their title.