RCB vs GT, IPL 2026 Final: Washington Sundar’s Controversial ‘Not Out’ Call Sparks Umpiring Debate

Washington Sundar's reprieve in the IPL 2026 final triggered a major umpiring debate. The third umpire overturned an on-field 'out' decision after ruling that Jordan Cox had not completed a clean catch, with replays suggesting the ball touched the grass. The verdict frustrated RCB and sparked widespread discussion over officiating consistency.

The Gujarat Titans (GT) all-rounder Washington Sundar’s survival after a contentious "not out" decision during the IPL 2026 final against Royal Challengers Bengaluru (RCB) has sparked a fierce debate officiating consistency.

After being put into bat first by RCB skipper Rajat Patidar at Ahmedabad’s Narendra Modi Stadium, the GT had a poor start to their innings as they lost key batters, including opener Sai Sudharsan (8), skipper Shubman Gill (10), Nishant Sindhu (20), and Jos Buttler (19) and they were reduced to 73/4 in 12.1 overs, putting them under pressure in the high-stakes final.

Thereafter, Washington Sundar and Arshad Khan (15) shared a brief 20-run partnership for the fifth wicket before the latter’s dismissal at 99/5, further stalling Gujarat's recovery and deepening the crisis for the Titans in the summit clash.

Sundar’s Not Out Call Sparks Controversy

As the Gujarat Titans struggled to build momentum, a pivotal moment came occurred when a low catch of Washington Sundar by Jordon Cox became a centre of controversy amid the IPL 2026 final. The incident took place on the final of the 10 over when Sundar attempted a flick off Jocab Duffy’s delivery, with the ball travelling to fine leg, where Cox was stationed.

Jordan Cox dived forward to complete what initially appeared to be a clean catch of Sundar and the on-field umpire ruled it as out. Washington Sundar was walking back to the dugout when he was asked to wait for a third-umpire review. The slow-motion replay suggested that ball became lodged awkwardly between Cox's fingers and made contact with the grass before he could secure full control.

The third-umpire overturned the initial decision, leaving RCB skipper Rajat Patidar unhappy as he was seen arguing with the on-field umpire over the perceived inconsistency of the ruling.

Gone... gone... DROPPED! 😱🤯

Big moment in the match as #WashingtonSundar is dropped in the deep by #JordanCox. 👀#TATAIPL 2026 FINAL | #RCBvGT | LIVE NOW 👉 https://t.co/nTKb3Qmpst pic.twitter.com/xUznFU4TBU

— Star Sports (@StarSportsIndia) May 31, 2026

Washington Sundar was batting on 4 off 7 balls when the on-field umpire initially raised his finger to signal ‘out’ before the GT all-rounder was called back to the crease. The third umpire’s decision to reverse the original decision after Jordon Cox’s diving effort at deep fine leg was deemed inconclusive, with replays showing the ball making contact with the grass before the substitute fielder could secure full control

The RCB camp was not happy with the third umpire’s decision, prompting Rajat Patidar to engage in an animated and prolonged discussion with the on-field umpires, as he felt the catch by Cox was legitimate.

Officiating Consistency Under the Spotlight

The third umpire’s decision to overturn the "out" call and rule Washington Sundar "not out" ignited a fierce debate on social media, especially X (formerly Twitter), with fans and cricket enthusiasts pointing out the stark difference in how seemingly identical low-catch scenarios have been adjudicated throughout the tournament.

Taking to their X handles, fans and cricket enthusiasts questioned the consistency of umpiring decisions, with many drawing comparisons to a similar catch taken by Jason Holder earlier in the tournament that was ruled out.

While some felt Washington was fortunate to survive, others argued the replay showed the ball touching the ground, making the third umpire's 'not out' decision justified, highlighting the inherent difficulty of ruling on ‘soft signals’ and grass-level catches in such high-pressure matches.

Washington Sundar given NOT OUT! 🤔
Cox didn't seem to have full control of that catch. 

Have seen similar ones given out in the past. 

Consistency in umpiring decisions matters. #Cricket #ipl #RCB #GT pic.twitter.com/eMvPghMOb7

— Nagarjuna Reddy (@Nagarjuna576) May 31, 2026

THE DRAMA: Washington Sundar got out on 4 off 7 balls.

Umpires checked for fair catch as ball touched the ground and Washington Sundar remains NOT OUT. pic.twitter.com/MOffLRJWOk

— Maina Singh (@Maina_Singhx77) May 31, 2026

When Jason Holder took the similar catch of Rajat Patidar in group stage match then it was given out & tonight when Jordan Cox took similar catch of Washington Sundar, it is given notout. Okay!

— Rajiv (@Rajiv1841) May 31, 2026

This is completely not out but given out

But Washington sundar catch is not out

Gems of umpiring 🤡🤡 pic.twitter.com/Z3xQmN3PN2

— 𝐑𝐂𝐁 𝐇𝐘𝐏𝐄 (@Alkohlic_149) May 31, 2026

Washington Sundar got a not out from Third Umpire 

But this looks under control #GTvsRCB #RCBvsGT pic.twitter.com/TFJ1cnCOnv

— Raja (@_raja_kumar) May 31, 2026

How is Washington Sundar catch a not out? @IPL 3rd umpire with all the technologies in the plate how is this blunder going to be accepted? If Jason is given not out then Washington was clearly out! Shameful umpiring that too in finale!#RCBvsGT@RCBTweets

— shash_22 (@shashiyer_22) May 31, 2026

Ground umpire gave it out to Washington Sundar, but the third umpire got it right.

The replay showed the ball touching the ground during the catch. Tough call, but the correct decision was not out.

What do you think about it, Out or Not out? pic.twitter.com/yIGeNMZirw

— Cricket Capital (@CricketCapital7) May 31, 2026

Meanwhile, the Gujarat Titans posted a total of 155/8 in 20 overs and set a 156-run target for the Royal Challengers Bengaluru to chase in the final. Washington Sundar’s unbeaten 50 off 37 balls eventually guided the GT to a respectable total after a poor start to their innings.

Rasikh Salam Dar led the RCB’s bowling attack with figures of 3/27 at an economy rate of 6.80 in his spell of four overs. Bhuvneshwar Kumar (2/29) and Josh Hazlewood (2/37) also played crucial roles in restricting the Gujarat Titans.