Amit Banerjee
Amit Banerjee, a reporter at CricketCountry, takes a keen interest in photography, travelling, technology, automobiles, food, and of course, cricket. He can be followed on Twitter @akb287.
Written by Amit Banerjee
Published: Sep 30, 2014, 04:16 AM (IST)
Edited: Sep 30, 2014, 10:33 AM (IST)
Sep 30, 2014
Sunil Narine getting reported for suspect bowling action during the match between Kolkata Knight Riders (KKR) and Dolphins in the ongoing Champions League Twenty20 (CLT20) sparked off a series of posts on social media platforms such as Twitter. The KKR off-spinner was reported by the on-field umpires Anil Chaudhary, Chettithody Shamshuddin and by the third umpire Kumar Dharmasena. It was one of his quicker deliveries that generated the suspicion.
Following were some of the tweets posted after the news of the event broke out:
I see yet another bowler has been called into question this time Sunil Narine…batsmen get on with it stop your moaning #itsaskill
— Alex Tudor (@alextudorcoach) September 29, 2014
So now Sunil Narine has been reported for a suspect action. What a load of nonsense. Who honestly thinks he’s a chucker and bad for cricket?
— John Etheridge (@JohnSunCricket) September 29, 2014
now that the crackdown on actions is in full swing, let us turn our attention to outsized bats, undersized boundaries and unfair switch hits
— Harsha Bhogle (@bhogleharsha) September 30, 2014
the interesting thing would be to know if the umpires wanted to report actions all these years………
— Harsha Bhogle (@bhogleharsha) September 30, 2014
Narine joins the list of bowlers with suspect actions…so, how many international wickets in total are under this cloud of chucking? #ajmal
— Aakash Chopra (@cricketaakash) September 30, 2014
Complete coverage of Sunil Narine reported for suspect action
Complete coverage of Champions League T20 (CLT20) 2014
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.