Cricket has become a popular game ever since it’s inception and as time passed by, there have been plenty of changes. Bearing in mind the dynamics of the sport, the technical aspect of the sport has also been looked upon. The game has become advanced and technologies of the highest quality is being applied.

One of the most talked about among them is the Decision Review System (DRS). However, while there’s a bright side to technology, it can be misguiding as well. As they say, technology can’t be foolproof.

Same has been the case with the DRS, the credentials of which have been questioned plenty of times. On a number of instances, players have had to bear the brunt of the errors on the field. The goof-ups have all the potential to turn around the fortunes of many.

In the article, let’s take a look at five instances of technical glitches in cricket: &#8211;

1. Mateesha Pathirana’s 175 km/h thunderbolt, 2020

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

Sri Lanka’s Mateesha Pathirana, who models his action on <a href="https://www.crictracker.com/lasith-malinga-is-my-guy-kevin-pietersen-while-picking-the-sri-lankan-as-greatest-ever-ipl-bowler/" target="_blank" rel="noopener noreferrer">Lasith Malinga</a>, grabbed the headlines in the 2020 edition of the U19 World Cup in South Africa. In the match against India, the youngster recorded a delivery, which showed 175 kmph on the Speedometer.

Numbers said that it was the fastest ball to be ever bowled in any form of cricket and had surpassed speedster Shoaib Akhtar. Yashasvi Jaiswal faced Pathirana’s delivery in the game. At first go, one couldn’t have been blamed for thinking that there’s something fishy in a 17-year-old hurling the thunderbolt.

Later, it was indeed revealed that there was a technical glitch while recording. Therefore, Shoaib’s 161.3 kmph (100 mph) in an ODI against England in the 2003 World Cup remained as the fastest delivery.

2. Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe, 1932

<img loading="lazy" class="size-full wp-image-415720" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Scoreboard-error-in-555-run-stand-between-Percy-Holmes-and-Herbert-Sutcliffe.jpg" alt="Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-415720" class="wp-caption-text">Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe. (Photo Source: Getty Images)</figcaption>

Back in 1898, Jack Brown and John Tunicliffe, while playing for Yorkshire, recorded the highest first-wicket partnership off 554 in first-class cricket. In 1932, Percy Holmes and Herbert Sutcliffe of Yorkshire itself, broke the record with a 555-run stand against Essex at Lenton, the latter’s home ground.

On the second day’s play, Sutcliffe’s four off Lawrie Eastman took them to the helm. Immediately after Sutcliffe got out, Brian Sellers, the Yorkshire skipper, declared. As the players reached the pavilion, the scoreboard clicked back by one run.

An enquiry then revealed that the scorers had made a mistake. It was then learned that umpire Tiger Smith had told Billy Ringrose, the Yorkshire scorer, that he missed a no-ball. In the end, all parties agreed and the score went to 555.

3. James Pattinson’s run-out in BBL 8, 2018

<img loading="lazy" class="size-full wp-image-415722" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/James-Pattinson’s-run-out-in-BBL-8.jpg" alt="James Pattinson’s run-out in BBL 8" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-415722" class="wp-caption-text">James Pattinson’s run-out in BBL 8. (Photo Source: Twitter)</figcaption>

James Pattinson’s run-out in the 2018-19 Big Bash League had all sorts of controversies etched to it. It took place in the match between the Brisbane Heat and the Adelaide Strikers at The Gabba. Pattinson dived into the crease, but third umpire Greg Davidson gave him out. The umpires, players and the commentators were left in confusion.

Chris Lynn, the Heat’s skipper, didn’t look happy. In the end, Pattinson was called back after Strikers’ skipper Colin Ingram took back the appeal after consultation with veteran fast bowler Ben Laughlin.

Later, Adam Gilchrist, on Fox Cricket, revealed that radio communication between third umpire Davidson and the on-field umpires, Simon Fry and Paul Wilson, dropped out completely after the ‘out’ decision was flashed on the giant screen.

4. Qazi Onik’s 160 km/h delivery, 2018

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

Another case of technical error came up in the 2018 edition of the U19 World Cup in <a href="https://www.facebook.com/crictracker/photos/pb.600228316674560.-2207520000../3481620041868692/?type=3&amp;theater" target="_blank" rel="noopener noreferrer">New Zealand</a>. It happened with Bangladesh fast bowler Qazi Onik in a match against Prithvi Shaw’s India. Onik, who generally clocks around the 140 mark, churned out a delivery at 160 kmph.

The left-armer bowled a beautiful out-swinger and Shaw’s stumps went for a walk with India’s score at 102 in the 18th over. Shaw was batting on 40 and it indeed needed a special delivery from Onik to get rid of the Indian skipper.

As far as the speed of the ball was concerned, it was shown ever before Onik sent down the leather. Hence, there wasn’t much doubt that it was a technical glitch. Nevertheless, Onik, who went on to play for the Dhaka Dynamites in the 2018-19 BPL, would be happy after pinning the well-set Shaw.

5. Sachin Tendulkar’s controversial dismissal in IPL 2011

<img loading="lazy" class="size-full wp-image-415726" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Sachin-Tendulkar.jpg" alt="Sachin Tendulkar" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-415726" class="wp-caption-text">Sachin Tendulkar. (Photo Source: INDRANIL MUKHERJEE/AFP via Getty Images)</figcaption>

Sachin Tendulkar’s 38th birthday wasn’t quite a memorable one for the Master Blaster. Not only did his spiritual guru, Shri Satya Sai Baba, pass away, he also fell victim to a technical goof-up from the umpire. It happened during the 2011 edition of the IPL in the match between the Mumbai Indians and Deccan Chargers.

He batted until the ninth over, but was dismissed by leg-spinner Amit Mishra. Off the second ball, he was caught down at long-off by Dale Steyn. The umpire then stopped him to check if Mishra had overstepped.

The first replay from the stump-cam showed it may be a no-ball. The replays from the mid-wicket camera wasn’t conclusive. But then the third replay from the covers showed that Mishra didn’t overstep. However, it wasn’t the proper replay as Sachin was at the non-striker’s end.

Cricket has become a popular game ever since it’s inception and as time passed by, there have been plenty of changes. Bearing in mind the dynamics of the sport, the technical aspect of the sport has also been looked upon. The game has become advanced and technologies of the highest quality is being applied.
One of the most talked about among them is the Decision Review System (DRS). However, while there’s a bright side to technology, it can be misguiding as well. As they say, technology can’t be foolproof.
Same has been the case with the DRS, the credentials of which have been questioned plenty of times. On a number of instances, players have had to bear the brunt of the errors on the field. The goof-ups have all the potential to turn around the fortunes of many.
<h3>In the article, let’s take a look at five instances of technical glitches in cricket: – </h3>
<h3>1. Mateesha Pathirana’s 175 km/h thunderbolt, 2020</h3>
<figure id="attachment_391256" aria-describedby="caption-attachment-391256" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-391256" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Matheesha-Pathirana.png" alt="Matheesha Pathirana" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-391256" class="wp-caption-text">Matheesha Pathirana. (Photo Source: Twitter)</figcaption></figure>
Sri Lanka’s Mateesha Pathirana, who models his action on <a href="https://www.crictracker.com/lasith-malinga-is-my-guy-kevin-pietersen-while-picking-the-sri-lankan-as-greatest-ever-ipl-bowler/" target="_blank" rel="noopener noreferrer">Lasith Malinga</a>, grabbed the headlines in the 2020 edition of the U19 World Cup in South Africa. In the match against India, the youngster recorded a delivery, which showed 175 kmph on the Speedometer.
Numbers said that it was the fastest ball to be ever bowled in any form of cricket and had surpassed speedster Shoaib Akhtar. Yashasvi Jaiswal faced Pathirana’s delivery in the game. At first go, one couldn’t have been blamed for thinking that there’s something fishy in a 17-year-old hurling the thunderbolt.
Later, it was indeed revealed that there was a technical glitch while recording. Therefore, Shoaib’s 161.3 kmph (100 mph) in an ODI against England in the 2003 World Cup remained as the fastest delivery.

<h3>2. Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe, 1932</h3>
<figure id="attachment_415720" aria-describedby="caption-attachment-415720" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-415720" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Scoreboard-error-in-555-run-stand-between-Percy-Holmes-and-Herbert-Sutcliffe.jpg" alt="Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-415720" class="wp-caption-text">Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe. (Photo Source: Getty Images)</figcaption></figure>
Back in 1898, Jack Brown and John Tunicliffe, while playing for Yorkshire, recorded the highest first-wicket partnership off 554 in first-class cricket. In 1932, Percy Holmes and Herbert Sutcliffe of Yorkshire itself, broke the record with a 555-run stand against Essex at Lenton, the latter’s home ground.
On the second day’s play, Sutcliffe’s four off Lawrie Eastman took them to the helm. Immediately after Sutcliffe got out, Brian Sellers, the Yorkshire skipper, declared. As the players reached the pavilion, the scoreboard clicked back by one run.
An enquiry then revealed that the scorers had made a mistake. It was then learned that umpire Tiger Smith had told Billy Ringrose, the Yorkshire scorer, that he missed a no-ball. In the end, all parties agreed and the score went to 555.

<h3>3. James Pattinson’s run-out in BBL 8, 2018</h3>
<figure id="attachment_415722" aria-describedby="caption-attachment-415722" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-415722" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/James-Pattinson’s-run-out-in-BBL-8.jpg" alt="James Pattinson’s run-out in BBL 8" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-415722" class="wp-caption-text">James Pattinson’s run-out in BBL 8. (Photo Source: Twitter)</figcaption></figure>
James Pattinson’s run-out in the 2018-19 Big Bash League had all sorts of controversies etched to it. It took place in the match between the Brisbane Heat and the Adelaide Strikers at The Gabba. Pattinson dived into the crease, but third umpire Greg Davidson gave him out. The umpires, players and the commentators were left in confusion.
Chris Lynn, the Heat’s skipper, didn’t look happy. In the end, Pattinson was called back after Strikers’ skipper Colin Ingram took back the appeal after consultation with veteran fast bowler Ben Laughlin.
Later, Adam Gilchrist, on Fox Cricket, revealed that radio communication between third umpire Davidson and the on-field umpires, Simon Fry and Paul Wilson, dropped out completely after the ‘out’ decision was flashed on the giant screen.

<h3>4. Qazi Onik’s 160 km/h delivery, 2018</h3>
<figure id="attachment_220841" aria-describedby="caption-attachment-220841" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-220841" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Qazi-Onik-160.jpg" alt="Qazi Onik" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-220841" class="wp-caption-text">Qazi Onik. (Photo Source: Twitter)</figcaption></figure>
Another case of technical error came up in the 2018 edition of the U19 World Cup in <a href="https://www.facebook.com/crictracker/photos/pb.600228316674560.-2207520000../3481620041868692/?type=3&amp;theater" target="_blank" rel="noopener noreferrer">New Zealand</a>. It happened with Bangladesh fast bowler Qazi Onik in a match against Prithvi Shaw’s India. Onik, who generally clocks around the 140 mark, churned out a delivery at 160 kmph.
The left-armer bowled a beautiful out-swinger and Shaw’s stumps went for a walk with India’s score at 102 in the 18th over. Shaw was batting on 40 and it indeed needed a special delivery from Onik to get rid of the Indian skipper.
As far as the speed of the ball was concerned, it was shown ever before Onik sent down the leather. Hence, there wasn’t much doubt that it was a technical glitch. Nevertheless, Onik, who went on to play for the Dhaka Dynamites in the 2018-19 BPL, would be happy after pinning the well-set Shaw.

<h3>5. Sachin Tendulkar’s controversial dismissal in IPL 2011</h3>
<figure id="attachment_415726" aria-describedby="caption-attachment-415726" class="wp-caption aligncenter" style="max-width: 100%; margin: 0;"><amp-img class="size-full wp-image-415726" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Sachin-Tendulkar.jpg" alt="Sachin Tendulkar" width="640" height="400" layout="responsive" style="max-width: 100%; margin: 0;"></amp-img><figcaption id="caption-attachment-415726" class="wp-caption-text">Sachin Tendulkar. (Photo Source: INDRANIL MUKHERJEE/AFP via Getty Images)</figcaption></figure>
Sachin Tendulkar’s 38th birthday wasn’t quite a memorable one for the Master Blaster. Not only did his spiritual guru, Shri Satya Sai Baba, pass away, he also fell victim to a technical goof-up from the umpire. It happened during the 2011 edition of the IPL in the match between the Mumbai Indians and Deccan Chargers.
He batted until the ninth over, but was dismissed by leg-spinner Amit Mishra. Off the second ball, he was caught down at long-off by Dale Steyn. The umpire then stopped him to check if Mishra had overstepped.
The first replay from the stump-cam showed it may be a no-ball. The replays from the mid-wicket camera wasn’t conclusive. But then the third replay from the covers showed that Mishra didn’t overstep. However, it wasn’t the proper replay as Sachin was at the non-striker’s end.

Cricket has become a popular game ever since it’s inception and as time passed by, there have been plenty of changes. Bearing in mind the dynamics of the sport, the technical aspect of the sport has also been looked upon. The game has become advanced and technologies of the highest quality is being applied.
One of the most talked about among them is the Decision Review System (DRS). However, while there’s a bright side to technology, it can be misguiding as well. As they say, technology can’t be foolproof.
Same has been the case with the DRS, the credentials of which have been questioned plenty of times. On a number of instances, players have had to bear the brunt of the errors on the field. The goof-ups have all the potential to turn around the fortunes of many.
<h3>In the article, let’s take a look at five instances of technical glitches in cricket: &#8211; </h3>
<h3>1. Mateesha Pathirana’s 175 km/h thunderbolt, 2020</h3>
<figure id="attachment_391256" aria-describedby="caption-attachment-391256" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-391256" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Matheesha-Pathirana.png" alt="Matheesha Pathirana" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-391256" class="wp-caption-text">Matheesha Pathirana. (Photo Source: Twitter)</figcaption></figure>
Sri Lanka’s Mateesha Pathirana, who models his action on <a href="https://www.crictracker.com/lasith-malinga-is-my-guy-kevin-pietersen-while-picking-the-sri-lankan-as-greatest-ever-ipl-bowler/" target="_blank" rel="noopener noreferrer">Lasith Malinga</a>, grabbed the headlines in the 2020 edition of the U19 World Cup in South Africa. In the match against India, the youngster recorded a delivery, which showed 175 kmph on the Speedometer.
Numbers said that it was the fastest ball to be ever bowled in any form of cricket and had surpassed speedster Shoaib Akhtar. Yashasvi Jaiswal faced Pathirana’s delivery in the game. At first go, one couldn’t have been blamed for thinking that there’s something fishy in a 17-year-old hurling the thunderbolt.
Later, it was indeed revealed that there was a technical glitch while recording. Therefore, Shoaib’s 161.3 kmph (100 mph) in an ODI against England in the 2003 World Cup remained as the fastest delivery.

<h3>2. Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe, 1932</h3>
<figure id="attachment_415720" aria-describedby="caption-attachment-415720" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-415720" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Scoreboard-error-in-555-run-stand-between-Percy-Holmes-and-Herbert-Sutcliffe.jpg" alt="Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-415720" class="wp-caption-text">Scoreboard error in 555-run stand between Percy Holmes and Herbert Sutcliffe. (Photo Source: Getty Images)</figcaption></figure>
Back in 1898, Jack Brown and John Tunicliffe, while playing for Yorkshire, recorded the highest first-wicket partnership off 554 in first-class cricket. In 1932, Percy Holmes and Herbert Sutcliffe of Yorkshire itself, broke the record with a 555-run stand against Essex at Lenton, the latter’s home ground.
On the second day’s play, Sutcliffe’s four off Lawrie Eastman took them to the helm. Immediately after Sutcliffe got out, Brian Sellers, the Yorkshire skipper, declared. As the players reached the pavilion, the scoreboard clicked back by one run.
An enquiry then revealed that the scorers had made a mistake. It was then learned that umpire Tiger Smith had told Billy Ringrose, the Yorkshire scorer, that he missed a no-ball. In the end, all parties agreed and the score went to 555.

<h3>3. James Pattinson’s run-out in BBL 8, 2018</h3>
<figure id="attachment_415722" aria-describedby="caption-attachment-415722" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-415722" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/James-Pattinson’s-run-out-in-BBL-8.jpg" alt="James Pattinson’s run-out in BBL 8" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-415722" class="wp-caption-text">James Pattinson’s run-out in BBL 8. (Photo Source: Twitter)</figcaption></figure>
James Pattinson’s run-out in the 2018-19 Big Bash League had all sorts of controversies etched to it. It took place in the match between the Brisbane Heat and the Adelaide Strikers at The Gabba. Pattinson dived into the crease, but third umpire Greg Davidson gave him out. The umpires, players and the commentators were left in confusion.
Chris Lynn, the Heat’s skipper, didn’t look happy. In the end, Pattinson was called back after Strikers’ skipper Colin Ingram took back the appeal after consultation with veteran fast bowler Ben Laughlin.
Later, Adam Gilchrist, on Fox Cricket, revealed that radio communication between third umpire Davidson and the on-field umpires, Simon Fry and Paul Wilson, dropped out completely after the ‘out’ decision was flashed on the giant screen.

<h3>4. Qazi Onik’s 160 km/h delivery, 2018</h3>
<figure id="attachment_220841" aria-describedby="caption-attachment-220841" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-220841" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Qazi-Onik-160.jpg" alt="Qazi Onik" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-220841" class="wp-caption-text">Qazi Onik. (Photo Source: Twitter)</figcaption></figure>
Another case of technical error came up in the 2018 edition of the U19 World Cup in <a href="https://www.facebook.com/crictracker/photos/pb.600228316674560.-2207520000../3481620041868692/?type=3&amp;theater" target="_blank" rel="noopener noreferrer">New Zealand</a>. It happened with Bangladesh fast bowler Qazi Onik in a match against Prithvi Shaw’s India. Onik, who generally clocks around the 140 mark, churned out a delivery at 160 kmph.
The left-armer bowled a beautiful out-swinger and Shaw’s stumps went for a walk with India’s score at 102 in the 18th over. Shaw was batting on 40 and it indeed needed a special delivery from Onik to get rid of the Indian skipper.
As far as the speed of the ball was concerned, it was shown ever before Onik sent down the leather. Hence, there wasn’t much doubt that it was a technical glitch. Nevertheless, Onik, who went on to play for the Dhaka Dynamites in the 2018-19 BPL, would be happy after pinning the well-set Shaw.

<h3>5. Sachin Tendulkar’s controversial dismissal in IPL 2011</h3>
<figure id="attachment_415726" aria-describedby="caption-attachment-415726" style="width: 640px" class="wp-caption aligncenter"><img loading="lazy" class="size-full wp-image-415726" src="https://crictracker-admin-panel-08032022.s3.ap-south-1.amazonaws.com/media/attachments/Sachin-Tendulkar.jpg" alt="Sachin Tendulkar" width="640" height="400" sizes="(max-width: 640px) 100vw, 640px"><figcaption id="caption-attachment-415726" class="wp-caption-text">Sachin Tendulkar. (Photo Source: INDRANIL MUKHERJEE/AFP via Getty Images)</figcaption></figure>
Sachin Tendulkar’s 38th birthday wasn’t quite a memorable one for the Master Blaster. Not only did his spiritual guru, Shri Satya Sai Baba, pass away, he also fell victim to a technical goof-up from the umpire. It happened during the 2011 edition of the IPL in the match between the Mumbai Indians and Deccan Chargers.
He batted until the ninth over, but was dismissed by leg-spinner Amit Mishra. Off the second ball, he was caught down at long-off by Dale Steyn. The umpire then stopped him to check if Mishra had overstepped.
The first replay from the stump-cam showed it may be a no-ball. The replays from the mid-wicket camera wasn’t conclusive. But then the third replay from the covers showed that Mishra didn’t overstep. However, it wasn’t the proper replay as Sachin was at the non-striker’s end.

Technology isn't foolproof!

5 instances of technical glitches in cricket

Cricket has become a popular game ever since it’s inception and as time passed by, there have been plenty of changes. Bearing in mind the dynamics