The <a href="https://www.crictracker.com/t20/ipl-indian-premier-league/" target="_blank" rel="noopener">Indian Premier League</a> (IPL) is the cricketing festival that keeps the entire country hooked. There is a lot of fervor surrounding the tournament in India, and every little thing that happens on the field is scrutinized heavily by pundits and fans.

In its 13-year history, the IPL has also had some umpiring decisions that were dubious and created controversies. And, some of these decisions have even gone on to have an effect on the result of the match as well. With the 14th edition of the IPL just 2 weeks away, let us take a look at-

5 controversial umpiring decisions in IPL

<img loading="lazy" class="size-full wp-image-327427" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Lasith-Malinga.jpg" alt="Lasith Malinga" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-327427" class="wp-caption-text">Lasith Malinga in IPL 2019 (Photo Source: Twitter)</figcaption>

Let us travel to 28th March 2019 to the encounter between <a href="https://www.crictracker.com/they-got-piyush-chawla-a-very-experienced-campaigner-parthiv-patel-on-spinners-importance-for-mumbai-indians/" target="_blank" rel="noopener">Mumbai Indians</a> (MI) and Royal Challengers Bangalore (RCB) to delve deeper into this incident. Let us have a brief idea about what happened in the entire match to understand the consequence of this umpiring error. The RCB side won the toss and asked the Mumbai Indians (MI) to bat first.

Led by a classy 48 from skipper Rohit Sharma and a blistering 14 ball 32* from Hardik Pandya, the Mumbai side posted a total of 187/8 on the board. The Bangalore side needed its batsmen to step up in a challenging run chase. And, the two batting wizards of RCB, Virat Kohli and Ab De Villiers went berserk on that day.

While Kohli scored 46 off 32 deliveries, De Villiers scored 70* off just 41 balls. But, in spite of the scintillating batting effort from the duo, the RCB side fell short by just 6 runs. And, that might have been due to a blatant umpiring error.

Off the last delivery of the innings, the Virat Kohli-led side needed 7 runs to win, and Shivam Dube was the batsman on strike. Malinga overstepped off the last ball of the match, but the umpire failed to notice it. Dube hit the ball towards Long On, and the batsmen did not run. Now, if the no-ball was awarded, a run would have been added to the RCB total, the final delivery would have been re bowled again and a Free Hit would have been awarded as well. And, if the no-ball had been called early by the umpire, the batsmen might have even crossed and De Villiers might have faced the final delivery. And who knows, in such a high-pressure situation and in the form that De Villiers was in, the result of the match might have been different.

4.The umpire wilts under ‘Mahi pressure’

<img loading="lazy" class="size-full wp-image-456543" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/David-Warner-MS-Dhoni-and-Paul-Reifell.jpg" alt="David Warner, MS Dhoni and Paul Reifell" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-456543" class="wp-caption-text">David Warner, MS Dhoni, and Paul Reifell on a wide ball decision in IPL 2020 (Photo Source: Twitter)</figcaption>

This was an incident that took place in the 29th match of the 2020 IPL edition between Chennai Super Kings (CSK) and Sun Risers Hyderabad (SRH). The CSK outfit won the toss and decided to get their willows out. Led by Shane Watson’s 38-ball 42 and a blazing 25* off just 10 deliveries by Ravindra Jadeja, the ‘Men in Yellow’ scored 167.

In reply, the SRH batsmen failed to step up. Apart from <a href="https://www.crictracker.com/heres-the-amazing-coincidence-between-wtc-final-dates-and-virat-kohli-and-kane-williamson/" target="_blank" rel="noopener">Kane Williamson</a>, who scored a 39 ball 57, there was not a single SRH batsman who could even cross the 25-run mark. But then, despite a brilliant half-century by the Kiwi legend, the Hyderabad outfit fell short of the target by 20 runs. And now, let us come to the controversial part.

Off the second ball of the 19th over, Shardul Thakur bowled a delivery that swung away from the batsman. The ball was clearly past the wide line, and the umpire was about to extend his arms to signal a wide. But then, CSK skipper MS Dhoni was not happy with it. Dhoni immediately gestured towards the umpire in anger, as if questioning the decision, and this gesture was enough for the umpire to change his decision. A delivery that went past the wide line was not given as a wide, due to the pressure exerted by the CSK legend.

<img loading="lazy" class="size-full wp-image-256336" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Jasprit-Bumrah-1.jpg" alt="Jasprit Bumrah" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-256336" class="wp-caption-text">Jasprit Bumrah in a match between RCB and MI (Photo Source: Twitter)</figcaption>

This was an absolute blunder that grabbed the attention of the cricketing world. On 17th April 2018, Mumbai Indians (MI) and Royal Challengers Bangalore (RCB) locked horns in a league match. The Mumbai outfit batted first and piled up a colossal total of 213 runs on the board, with skipper <a href="https://www.crictracker.com/herschelle-gibbs-picks-a-better-batsman-between-rohit-sharma-and-virat-kohli/" target="_blank" rel="noopener">Rohit Sharma</a> scoring 94 off just 52 deliveries.

In reply, in spite of a brilliant 92* from the legendary Virat Kohli, the RCB side could manage to score just 167. But then, off the last ball of the 18th over of RCB’s innings, there was an umpiring error, and it was a blatant one. Jasprit Bumrah bowled a short delivery, and Umesh Yadav swung the bat wildly. The ball took the outside edge of his willow and went straight to Rohit Sharma, who completed the catch.

But then, the umpire was not sure about the legitimacy of the delivery and wanted to make sure that Bumrah’s foot was behind the crease and the delivery was a fair one. The replays confirmed that it was a fair delivery. So, what was the problem?

The problem was, in the replay that was shown, Umesh Yadav was not the man on strike. The third umpire had actually seen the replay of some other delivery, where Yadav was clearly seen standing at the opposite end (non-striker’s end) next to Bumrah. Yes, mistakes happen in sport. But this was one occasion where the third umpire was totally careless.

<img loading="lazy" class="size-full wp-image-243156" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Kane-Williamson-3.jpg" alt="Kane Williamson" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-243156" class="wp-caption-text">Kane Williamson of SRH plays a shot on Shardul Thakur&#8217;s delivery (Photo Source: Twitter)</figcaption>

Kane Williamson was at the receiving end of a poor decision from the leg umpire. And, when a match goes down to the wire and a side is defeated by just 4 runs, these errors become extremely costly. This incident took place on 22nd April 2018, in an encounter between <a href="https://www.crictracker.com/you-can-never-count-out-csk-and-ms-dhoni-parthiv-patel/" target="_blank" rel="noopener">Chennai Super Kings (CSK) </a>and Sun Risers Hyderabad (SRH). On the second ball of the 17th over of the SRH innings, Shardul Thakur bowled a delivery that was above Williamson’s waist. But, to everyone’s surprise, the leg umpire declared that it was a fair delivery. He could have referred the decision to the third umpire to get more clarity, but he refused to do so.

A no-ball would have not only meant that the SRH side would have got an extra delivery, but it would have also meant that the ‘Orange Army’ would have also got a Free Hit. But due to an error from the leg umpire, the CSK side got away with it.

As far as the match is concerned, the Chennai outfit batted first and scored 183 runs on the board. The main contributor for the ‘Yellow Brigade’ was Ambati Rayudu, who scored a rampaging 79 at a strike rate of 213.51. In reply, the SRH side finished with a total of 178/6 in their allotted 20 overs and lost a humdinger of a clash in spite of Williamson’s classy 84.

1.A wrong short-run call changes the result of a match!

<img loading="lazy" class="size-full wp-image-447388" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Short-run.jpg" alt="Short run" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-447388" class="wp-caption-text">Short run. (Photo Source: Disney+Hotstar VIP)</figcaption>

The IPL encounter between the Punjab Kings (PBKS) and the Delhi Capitals (DC) ended in a pulsating tie on 20th September 2020. The match went into the Super Over, and the Delhi outfit won the match. But then, a wrong short-run call was made off the third ball of the 19th over of the Punjab innings.

<a href="https://www.crictracker.com/mayank-agarwal-makes-a-blunder-while-wishing-jasprit-bumrah-and-sanjana-ganesan-on-their-wedding/" target="_blank" rel="noopener">Mayank Agarwal</a> ran a couple off that delivery, but the umpire called a short run as he felt that Chris Jordan’s bat had not crossed the line. But then, replays showed that Jordan had completed the run, as the bat was clearly past the crease. This created a huge controversy, as this decision completely changed the result of the match.

In fact, Indian batting legend Virender Sehwag cheekily suggested that the umpire who made the decision of awarding the short run should be declared as the Man of the Match.

You can see Sehwag’s hilarious tweet below

I don’t agree with the man of the match choice . The umpire who gave this short run should have been man of the match. Short Run nahin tha. And that was the difference. <a href="https://twitter.com/hashtag/DCvKXIP?src=hash&amp;ref_src=twsrc%5Etfw">#DCvKXIP</a> <a href="https://t.co/7u7KKJXCLb">pic.twitter.com/7u7KKJXCLb</a>&mdash; Virender Sehwag (@virendersehwag) <a href="https://twitter.com/virendersehwag/status/1307750803201863681?ref_src=twsrc%5Etfw">September 20, 2020</a>

Let us get into the facts of the match. The Delhi Capitals (DC) batted first and posted 157/8 on the board. Marcus Stoinis went berserk with the willow, and scored 53 off just 21 deliveries for the Shreyas Iyer led side. The Punjab Kings&#8217; (PBKS) innings was about one man, Mayank Agarwal. The opener plundered a 60 ball 89 but did not receive any support from his teammates. In fact, the next highest run-scorer for the Punjab outfit was Krishnappa Gowtham, who scored 20. The Punjab side too, finished with exactly the same total, 157/8.

But then, in the Super Over, it was the Delhi outfit that came out on top. In the Super Over, the Punjab Kings (PBKS) managed to score just 2 runs, and the Delhi side chased it down with ease and won the match. But then, if the short-run call was not made, the match would have not even gone to the Super Over, isn’t it?

The <a href="https://www.crictracker.com/t20/ipl-indian-premier-league/" target="_blank" rel="noopener">Indian Premier League</a> (IPL) is the cricketing festival that keeps the entire country hooked. There is a lot of fervor surrounding the tournament in India, and every little thing that happens on the field is scrutinized heavily by pundits and fans.
In its 13-year history, the IPL has also had some umpiring decisions that were dubious and created controversies. And, some of these decisions have even gone on to have an effect on the result of the match as well. With the 14th edition of the IPL just 2 weeks away, let us take a look at-
<h2>5 controversial umpiring decisions in IPL</h2>
<h3>5.That’s a No Ball Malinga!</h3>
<figure id="attachment_327427" aria-describedby="caption-attachment-327427" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-327427" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Lasith-Malinga.jpg" alt="Lasith Malinga" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-327427" class="wp-caption-text">Lasith Malinga in IPL 2019 (Photo Source: Twitter)</figcaption></figure>
Let us travel to 28th March 2019 to the encounter between <a href="https://www.crictracker.com/they-got-piyush-chawla-a-very-experienced-campaigner-parthiv-patel-on-spinners-importance-for-mumbai-indians/" target="_blank" rel="noopener">Mumbai Indians</a> (MI) and Royal Challengers Bangalore (RCB) to delve deeper into this incident. Let us have a brief idea about what happened in the entire match to understand the consequence of this umpiring error. The RCB side won the toss and asked the Mumbai Indians (MI) to bat first.
Led by a classy 48 from skipper Rohit Sharma and a blistering 14 ball 32* from Hardik Pandya, the Mumbai side posted a total of 187/8 on the board. The Bangalore side needed its batsmen to step up in a challenging run chase. And, the two batting wizards of RCB, Virat Kohli and Ab De Villiers went berserk on that day.
While Kohli scored 46 off 32 deliveries, De Villiers scored 70* off just 41 balls. But, in spite of the scintillating batting effort from the duo, the RCB side fell short by just 6 runs. And, that might have been due to a blatant umpiring error.
Off the last delivery of the innings, the Virat Kohli-led side needed 7 runs to win, and Shivam Dube was the batsman on strike. Malinga overstepped off the last ball of the match, but the umpire failed to notice it. Dube hit the ball towards Long On, and the batsmen did not run. Now, if the no-ball was awarded, a run would have been added to the RCB total, the final delivery would have been re bowled again and a Free Hit would have been awarded as well. And, if the no-ball had been called early by the umpire, the batsmen might have even crossed and De Villiers might have faced the final delivery. And who knows, in such a high-pressure situation and in the form that De Villiers was in, the result of the match might have been different.

<h3>4.The umpire wilts under ‘Mahi pressure’</h3>
<figure id="attachment_456543" aria-describedby="caption-attachment-456543" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-456543" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/David-Warner-MS-Dhoni-and-Paul-Reifell.jpg" alt="David Warner, MS Dhoni and Paul Reifell" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-456543" class="wp-caption-text">David Warner, MS Dhoni, and Paul Reifell on a wide ball decision in IPL 2020 (Photo Source: Twitter)</figcaption></figure>
This was an incident that took place in the 29th match of the 2020 IPL edition between Chennai Super Kings (CSK) and Sun Risers Hyderabad (SRH). The CSK outfit won the toss and decided to get their willows out. Led by Shane Watson’s 38-ball 42 and a blazing 25* off just 10 deliveries by Ravindra Jadeja, the ‘Men in Yellow’ scored 167.
In reply, the SRH batsmen failed to step up. Apart from <a href="https://www.crictracker.com/heres-the-amazing-coincidence-between-wtc-final-dates-and-virat-kohli-and-kane-williamson/" target="_blank" rel="noopener">Kane Williamson</a>, who scored a 39 ball 57, there was not a single SRH batsman who could even cross the 25-run mark. But then, despite a brilliant half-century by the Kiwi legend, the Hyderabad outfit fell short of the target by 20 runs. And now, let us come to the controversial part.
Off the second ball of the 19th over, Shardul Thakur bowled a delivery that swung away from the batsman. The ball was clearly past the wide line, and the umpire was about to extend his arms to signal a wide. But then, CSK skipper MS Dhoni was not happy with it. Dhoni immediately gestured towards the umpire in anger, as if questioning the decision, and this gesture was enough for the umpire to change his decision. A delivery that went past the wide line was not given as a wide, due to the pressure exerted by the CSK legend.

<h3>3.The no-ball replay that caused a stir</h3>
<figure id="attachment_256336" aria-describedby="caption-attachment-256336" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-256336" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Jasprit-Bumrah-1.jpg" alt="Jasprit Bumrah" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-256336" class="wp-caption-text">Jasprit Bumrah in a match between RCB and MI (Photo Source: Twitter)</figcaption></figure>
This was an absolute blunder that grabbed the attention of the cricketing world. On 17th April 2018, Mumbai Indians (MI) and Royal Challengers Bangalore (RCB) locked horns in a league match. The Mumbai outfit batted first and piled up a colossal total of 213 runs on the board, with skipper <a href="https://www.crictracker.com/herschelle-gibbs-picks-a-better-batsman-between-rohit-sharma-and-virat-kohli/" target="_blank" rel="noopener">Rohit Sharma</a> scoring 94 off just 52 deliveries.
In reply, in spite of a brilliant 92* from the legendary Virat Kohli, the RCB side could manage to score just 167. But then, off the last ball of the 18th over of RCB’s innings, there was an umpiring error, and it was a blatant one. Jasprit Bumrah bowled a short delivery, and Umesh Yadav swung the bat wildly. The ball took the outside edge of his willow and went straight to Rohit Sharma, who completed the catch.
But then, the umpire was not sure about the legitimacy of the delivery and wanted to make sure that Bumrah’s foot was behind the crease and the delivery was a fair one. The replays confirmed that it was a fair delivery. So, what was the problem?
The problem was, in the replay that was shown, Umesh Yadav was not the man on strike. The third umpire had actually seen the replay of some other delivery, where Yadav was clearly seen standing at the opposite end (non-striker’s end) next to Bumrah. Yes, mistakes happen in sport. But this was one occasion where the third umpire was totally careless.

<h3>2.That’s over the waist, clearly!</h3>
<figure id="attachment_243156" aria-describedby="caption-attachment-243156" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-243156" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Kane-Williamson-3.jpg" alt="Kane Williamson" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-243156" class="wp-caption-text">Kane Williamson of SRH plays a shot on Shardul Thakur’s delivery (Photo Source: Twitter)</figcaption></figure>
Kane Williamson was at the receiving end of a poor decision from the leg umpire. And, when a match goes down to the wire and a side is defeated by just 4 runs, these errors become extremely costly. This incident took place on 22nd April 2018, in an encounter between <a href="https://www.crictracker.com/you-can-never-count-out-csk-and-ms-dhoni-parthiv-patel/" target="_blank" rel="noopener">Chennai Super Kings (CSK) </a>and Sun Risers Hyderabad (SRH). On the second ball of the 17th over of the SRH innings, Shardul Thakur bowled a delivery that was above Williamson’s waist. But, to everyone’s surprise, the leg umpire declared that it was a fair delivery. He could have referred the decision to the third umpire to get more clarity, but he refused to do so.
A no-ball would have not only meant that the SRH side would have got an extra delivery, but it would have also meant that the ‘Orange Army’ would have also got a Free Hit. But due to an error from the leg umpire, the CSK side got away with it.
As far as the match is concerned, the Chennai outfit batted first and scored 183 runs on the board. The main contributor for the ‘Yellow Brigade’ was Ambati Rayudu, who scored a rampaging 79 at a strike rate of 213.51. In reply, the SRH side finished with a total of 178/6 in their allotted 20 overs and lost a humdinger of a clash in spite of Williamson’s classy 84.

<h3>1.A wrong short-run call changes the result of a match!</h3>
<figure id="attachment_447388" aria-describedby="caption-attachment-447388" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-447388" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Short-run.jpg" alt="Short run" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-447388" class="wp-caption-text">Short run. (Photo Source: Disney+Hotstar VIP)</figcaption></figure>
The IPL encounter between the Punjab Kings (PBKS) and the Delhi Capitals (DC) ended in a pulsating tie on 20th September 2020. The match went into the Super Over, and the Delhi outfit won the match. But then, a wrong short-run call was made off the third ball of the 19th over of the Punjab innings.
<a href="https://www.crictracker.com/mayank-agarwal-makes-a-blunder-while-wishing-jasprit-bumrah-and-sanjana-ganesan-on-their-wedding/" target="_blank" rel="noopener">Mayank Agarwal</a> ran a couple off that delivery, but the umpire called a short run as he felt that Chris Jordan’s bat had not crossed the line. But then, replays showed that Jordan had completed the run, as the bat was clearly past the crease. This created a huge controversy, as this decision completely changed the result of the match.
In fact, Indian batting legend Virender Sehwag cheekily suggested that the umpire who made the decision of awarding the short run should be declared as the Man of the Match.
You can see Sehwag’s hilarious tweet below
<amp-twitter data-width="500" data-dnt="true" height="694" width="486" layout="responsive" data-tweetid="1307750803201863681?ref_src=twsrc%5Etfw"></amp-twitter>

Let us get into the facts of the match. The Delhi Capitals (DC) batted first and posted 157/8 on the board. Marcus Stoinis went berserk with the willow, and scored 53 off just 21 deliveries for the Shreyas Iyer led side. The Punjab Kings’ (PBKS) innings was about one man, Mayank Agarwal. The opener plundered a 60 ball 89 but did not receive any support from his teammates. In fact, the next highest run-scorer for the Punjab outfit was Krishnappa Gowtham, who scored 20. The Punjab side too, finished with exactly the same total, 157/8.
But then, in the Super Over, it was the Delhi outfit that came out on top. In the Super Over, the Punjab Kings (PBKS) managed to score just 2 runs, and the Delhi side chased it down with ease and won the match. But then, if the short-run call was not made, the match would have not even gone to the Super Over, isn’t it?
&nbsp;

The <a href="https://www.crictracker.com/t20/ipl-indian-premier-league/" target="_blank" rel="noopener">Indian Premier League</a> (IPL) is the cricketing festival that keeps the entire country hooked. There is a lot of fervor surrounding the tournament in India, and every little thing that happens on the field is scrutinized heavily by pundits and fans.
In its 13-year history, the IPL has also had some umpiring decisions that were dubious and created controversies. And, some of these decisions have even gone on to have an effect on the result of the match as well. With the 14th edition of the IPL just 2 weeks away, let us take a look at-
<h2>5 controversial umpiring decisions in IPL</h2>
<h3>5.That’s a No Ball Malinga!</h3>
<figure id="attachment_327427" aria-describedby="caption-attachment-327427" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-327427" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Lasith-Malinga.jpg" alt="Lasith Malinga" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-327427" class="wp-caption-text">Lasith Malinga in IPL 2019 (Photo Source: Twitter)</figcaption></figure>
Let us travel to 28th March 2019 to the encounter between <a href="https://www.crictracker.com/they-got-piyush-chawla-a-very-experienced-campaigner-parthiv-patel-on-spinners-importance-for-mumbai-indians/" target="_blank" rel="noopener">Mumbai Indians</a> (MI) and Royal Challengers Bangalore (RCB) to delve deeper into this incident. Let us have a brief idea about what happened in the entire match to understand the consequence of this umpiring error. The RCB side won the toss and asked the Mumbai Indians (MI) to bat first.
Led by a classy 48 from skipper Rohit Sharma and a blistering 14 ball 32* from Hardik Pandya, the Mumbai side posted a total of 187/8 on the board. The Bangalore side needed its batsmen to step up in a challenging run chase. And, the two batting wizards of RCB, Virat Kohli and Ab De Villiers went berserk on that day.
While Kohli scored 46 off 32 deliveries, De Villiers scored 70* off just 41 balls. But, in spite of the scintillating batting effort from the duo, the RCB side fell short by just 6 runs. And, that might have been due to a blatant umpiring error.
Off the last delivery of the innings, the Virat Kohli-led side needed 7 runs to win, and Shivam Dube was the batsman on strike. Malinga overstepped off the last ball of the match, but the umpire failed to notice it. Dube hit the ball towards Long On, and the batsmen did not run. Now, if the no-ball was awarded, a run would have been added to the RCB total, the final delivery would have been re bowled again and a Free Hit would have been awarded as well. And, if the no-ball had been called early by the umpire, the batsmen might have even crossed and De Villiers might have faced the final delivery. And who knows, in such a high-pressure situation and in the form that De Villiers was in, the result of the match might have been different.

<h3>4.The umpire wilts under ‘Mahi pressure’</h3>
<figure id="attachment_456543" aria-describedby="caption-attachment-456543" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-456543" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/David-Warner-MS-Dhoni-and-Paul-Reifell.jpg" alt="David Warner, MS Dhoni and Paul Reifell" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-456543" class="wp-caption-text">David Warner, MS Dhoni, and Paul Reifell on a wide ball decision in IPL 2020 (Photo Source: Twitter)</figcaption></figure>
This was an incident that took place in the 29th match of the 2020 IPL edition between Chennai Super Kings (CSK) and Sun Risers Hyderabad (SRH). The CSK outfit won the toss and decided to get their willows out. Led by Shane Watson’s 38-ball 42 and a blazing 25* off just 10 deliveries by Ravindra Jadeja, the ‘Men in Yellow’ scored 167.
In reply, the SRH batsmen failed to step up. Apart from <a href="https://www.crictracker.com/heres-the-amazing-coincidence-between-wtc-final-dates-and-virat-kohli-and-kane-williamson/" target="_blank" rel="noopener">Kane Williamson</a>, who scored a 39 ball 57, there was not a single SRH batsman who could even cross the 25-run mark. But then, despite a brilliant half-century by the Kiwi legend, the Hyderabad outfit fell short of the target by 20 runs. And now, let us come to the controversial part.
Off the second ball of the 19th over, Shardul Thakur bowled a delivery that swung away from the batsman. The ball was clearly past the wide line, and the umpire was about to extend his arms to signal a wide. But then, CSK skipper MS Dhoni was not happy with it. Dhoni immediately gestured towards the umpire in anger, as if questioning the decision, and this gesture was enough for the umpire to change his decision. A delivery that went past the wide line was not given as a wide, due to the pressure exerted by the CSK legend.

<h3>3.The no-ball replay that caused a stir</h3>
<figure id="attachment_256336" aria-describedby="caption-attachment-256336" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-256336" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Jasprit-Bumrah-1.jpg" alt="Jasprit Bumrah" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-256336" class="wp-caption-text">Jasprit Bumrah in a match between RCB and MI (Photo Source: Twitter)</figcaption></figure>
This was an absolute blunder that grabbed the attention of the cricketing world. On 17th April 2018, Mumbai Indians (MI) and Royal Challengers Bangalore (RCB) locked horns in a league match. The Mumbai outfit batted first and piled up a colossal total of 213 runs on the board, with skipper <a href="https://www.crictracker.com/herschelle-gibbs-picks-a-better-batsman-between-rohit-sharma-and-virat-kohli/" target="_blank" rel="noopener">Rohit Sharma</a> scoring 94 off just 52 deliveries.
In reply, in spite of a brilliant 92* from the legendary Virat Kohli, the RCB side could manage to score just 167. But then, off the last ball of the 18th over of RCB’s innings, there was an umpiring error, and it was a blatant one. Jasprit Bumrah bowled a short delivery, and Umesh Yadav swung the bat wildly. The ball took the outside edge of his willow and went straight to Rohit Sharma, who completed the catch.
But then, the umpire was not sure about the legitimacy of the delivery and wanted to make sure that Bumrah’s foot was behind the crease and the delivery was a fair one. The replays confirmed that it was a fair delivery. So, what was the problem?
The problem was, in the replay that was shown, Umesh Yadav was not the man on strike. The third umpire had actually seen the replay of some other delivery, where Yadav was clearly seen standing at the opposite end (non-striker’s end) next to Bumrah. Yes, mistakes happen in sport. But this was one occasion where the third umpire was totally careless.

<h3>2.That’s over the waist, clearly!</h3>
<figure id="attachment_243156" aria-describedby="caption-attachment-243156" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-243156" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Kane-Williamson-3.jpg" alt="Kane Williamson" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-243156" class="wp-caption-text">Kane Williamson of SRH plays a shot on Shardul Thakur&#8217;s delivery (Photo Source: Twitter)</figcaption></figure>
Kane Williamson was at the receiving end of a poor decision from the leg umpire. And, when a match goes down to the wire and a side is defeated by just 4 runs, these errors become extremely costly. This incident took place on 22nd April 2018, in an encounter between <a href="https://www.crictracker.com/you-can-never-count-out-csk-and-ms-dhoni-parthiv-patel/" target="_blank" rel="noopener">Chennai Super Kings (CSK) </a>and Sun Risers Hyderabad (SRH). On the second ball of the 17th over of the SRH innings, Shardul Thakur bowled a delivery that was above Williamson’s waist. But, to everyone’s surprise, the leg umpire declared that it was a fair delivery. He could have referred the decision to the third umpire to get more clarity, but he refused to do so.
A no-ball would have not only meant that the SRH side would have got an extra delivery, but it would have also meant that the ‘Orange Army’ would have also got a Free Hit. But due to an error from the leg umpire, the CSK side got away with it.
As far as the match is concerned, the Chennai outfit batted first and scored 183 runs on the board. The main contributor for the ‘Yellow Brigade’ was Ambati Rayudu, who scored a rampaging 79 at a strike rate of 213.51. In reply, the SRH side finished with a total of 178/6 in their allotted 20 overs and lost a humdinger of a clash in spite of Williamson’s classy 84.

<h3>1.A wrong short-run call changes the result of a match!</h3>
<figure id="attachment_447388" aria-describedby="caption-attachment-447388" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-447388" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Short-run.jpg" alt="Short run" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-447388" class="wp-caption-text">Short run. (Photo Source: Disney+Hotstar VIP)</figcaption></figure>
The IPL encounter between the Punjab Kings (PBKS) and the Delhi Capitals (DC) ended in a pulsating tie on 20th September 2020. The match went into the Super Over, and the Delhi outfit won the match. But then, a wrong short-run call was made off the third ball of the 19th over of the Punjab innings.
<a href="https://www.crictracker.com/mayank-agarwal-makes-a-blunder-while-wishing-jasprit-bumrah-and-sanjana-ganesan-on-their-wedding/" target="_blank" rel="noopener">Mayank Agarwal</a> ran a couple off that delivery, but the umpire called a short run as he felt that Chris Jordan’s bat had not crossed the line. But then, replays showed that Jordan had completed the run, as the bat was clearly past the crease. This created a huge controversy, as this decision completely changed the result of the match.
In fact, Indian batting legend Virender Sehwag cheekily suggested that the umpire who made the decision of awarding the short run should be declared as the Man of the Match.
You can see Sehwag’s hilarious tweet below
<blockquote class="twitter-tweet" data-width="500" data-dnt="true">
I don’t agree with the man of the match choice . The umpire who gave this short run should have been man of the match. Short Run nahin tha. And that was the difference. <a href="https://twitter.com/hashtag/DCvKXIP?src=hash&amp;ref_src=twsrc%5Etfw">#DCvKXIP</a> <a href="https://t.co/7u7KKJXCLb">pic.twitter.com/7u7KKJXCLb</a>
&mdash; Virender Sehwag (@virendersehwag) <a href="https://twitter.com/virendersehwag/status/1307750803201863681?ref_src=twsrc%5Etfw">September 20, 2020</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
Let us get into the facts of the match. The Delhi Capitals (DC) batted first and posted 157/8 on the board. Marcus Stoinis went berserk with the willow, and scored 53 off just 21 deliveries for the Shreyas Iyer led side. The Punjab Kings&#8217; (PBKS) innings was about one man, Mayank Agarwal. The opener plundered a 60 ball 89 but did not receive any support from his teammates. In fact, the next highest run-scorer for the Punjab outfit was Krishnappa Gowtham, who scored 20. The Punjab side too, finished with exactly the same total, 157/8.
But then, in the Super Over, it was the Delhi outfit that came out on top. In the Super Over, the Punjab Kings (PBKS) managed to score just 2 runs, and the Delhi side chased it down with ease and won the match. But then, if the short-run call was not made, the match would have not even gone to the Super Over, isn’t it?
&nbsp;

Some of these umpiring decisions have even gone on to have an effect on the result of the match.

IPL: Top 5 controversial umpiring decisions in tournament history

In its 13-year history, the IPL has also had some umpiring decisions that were dubious and created controversies in the tournament.