On May 1, 2025, during the 50th match of the Indian Premier League (IPL) 2025 at Jaipur’s Sawai Mansingh Stadium, a controversial Decision Review System (DRS) call involving Mumbai Indians (MI) star batter Rohit Sharma became the focal point of heated debate.
The incident, occurring early in MI’s innings against Rajasthan Royals (RR), not only saved Rohit from an early dismissal but also played a significant role in MI’s commanding 100-run victory. As fans took to social media to express outrage and question the umpiring, the episode highlighted the complexities of DRS regulations and their impact on high-stakes matches.
The DRS Incident: What Happened?
In the second over of MI’s innings, with the score at 7, Rohit Sharma faced a length delivery from RR’s left-arm pacer Fazalhaq Farooqi. The ball rapped him on the pads, and the on-field umpire raised his finger, adjudging him LBW. Rohit Sharma, appearing hesitant, consulted his opening partner Ryan Rickelton before signaling for a DRS review. The controversy arose when replays showed the DRS timer, displayed on the broadcast, reaching zero just as Rohit made the “T” sign, leading many to believe the review was requested too late.
Despite the apparent delay, the third umpire proceeded with the review. Ball-tracking technology revealed that the ball had pitched marginally outside the leg stump, with 50% of the ball outside the line, overturning the on-field decision. Rohit, reprieved on 7, breathed a sigh of relief and continued his innings, much to the chagrin of RR fans and neutrals watching.
Rohit Sharma took the DRS after time ran out. How can the Umpire allow him to use DRS after time expired? Will they allow this if it was a RR batter?
Umpiring Indians 🤡 pic.twitter.com/cBFkiWiHzx
— 𝐁𝐑𝐔𝐓𝐔 (@Brutu24) May 1, 2025
DRS Rules and the Timing Controversy
The IPL’s DRS regulations, aligned with International Cricket Council (ICC) standards, stipulate that a team has 15 seconds to request a review after the on-field umpire’s decision. The batting side or fielding captain must signal a “T” to the umpire within this timeframe. If the umpires believe the request is made after the 15-second limit, they are required to decline it. In Rohit’s case, the contention centered on whether his signal was timely.
Video evidence, as highlighted in a clip shared on the official IPL website (IPL T20), showed Rohit beginning his hand movement for the “T” sign just as the timer approached zero. Some reports suggest that his signal initiation was within the 15-second window, even if the completion coincided with the timer’s expiration. This interpretation likely influenced the umpires’ decision to allow the review, adhering to the rule’s emphasis on the start of the signal.
However, the broadcast timer’s display of zero fueled perceptions of a late call, igniting a storm on social media. Fans argued that the umpires showed leniency, possibly due to MI’s stature or Rohit’s influence, with some questioning, “What’s the point of having a timer?” Others countered that the umpires’ discretion in such marginal cases is part of the game’s officiating nuances.
Impact on the Match
The successful DRS review proved to be a game-changer. Had Rohit been dismissed for 7, MI’s innings could have taken a different trajectory, potentially disrupting their momentum. Instead, Rohit capitalized on the reprieve, scoring a fluent 53 off 36 balls, including nine boundaries. His knock was characterized by elegant drives and precise placement, showcasing his class as one of the IPL’s most prolific run-scorers.
Rohit’s innings laid the foundation for MI’s formidable total of 217/2. He forged a 116-run opening partnership with Ryan Rickelton, who contributed 61 off 38 balls with seven fours and three sixes. This stand set a solid platform, allowing Suryakumar Yadav (48* off 23) and Hardik Pandya (48* off 23) to unleash a late onslaught, propelling MI to the joint-highest IPL total at Jaipur. RR, in response, collapsed to 117 in 16.1 overs, with Jofra Archer’s 30 being their only notable contribution, highlighting the match’s one-sided nature.
Fan and Social Media Reactions
The DRS incident triggered a polarized response on social media platforms like X. Many fans expressed frustration, accusing the umpires of bias towards MI. An X post by user stated, “It was quite obvious that the time was already up, and the review was invalid. But Rohit Sharma survives”. Another user, shared a video clip, commenting, “Rohit Sharma took a review in the last seconds. This is Rohit DRS System #RRvsMI”.
Conversely, some fans defended the decision, arguing that the umpires correctly interpreted the rule based on the initiation of Rohit’s signal. The debate underscored the challenges of real-time officiating and the reliance on broadcast timers, which may not always align perfectly with the umpires’ perspective.
Rohit Sharma’s DRS controversy added a layer of drama to an already dominant performance by Mumbai Indians against Rajasthan Royals. While the decision to allow the review sparked outrage among some fans, it also showcased the fine margins that can define T20 cricket. Rohit’s subsequent 53, a cornerstone of MI’s 217/2, underscored the significance of the reprieve. As the IPL continues to evolve, this incident serves as a reminder of the challenges in balancing technology, rules, and human judgment in the high-pressure world of professional cricket.
Also Read: RR vs MI: MI’s Batting Blitz and Bowling Mastery Sink RR By 100 Runs