Virat Kohli is among the greatest that have ever graced the game of cricket. His excellent batting skills and attitude have garnered millions of followers both in India and abroad. Popularity is such that even the smallest of actions from his side creates a flutter in the media. A new post from him or a fresh look, or even his mere presence on social media becomes the talk of the town.
Virat Kohli had liked an Instagram post by the TV actress Avneet Kaur, and the online world caught fire with discussions overnight. With Kohli clarifying the whole affair of him liking the post as the result of an algorithm glitch, the topic continued to stay in the limelight. Now, Rahul Vaidya has come forth with a sly comment on Kohli. Here's what transpired.
Scarcely two days had elapsed since Virat had cleared the air regarding the Avneet post like, and yet another controversy arose. Rahul Vaidya uploaded a video in which he made fun of Virat's explanation in a veiled manner. He said that the same Instagram algorithm that liked Avneet's pictures also blocked him from Virat's account. This is not the very first time Rahul stated about getting blocked; he stated so quite a few times before.
Soon after Rahul's video became viral, the singer came under heavy Abuse by Virat's fans. But Rahul didn't keep quiet and went back at the trolls just like that.
Also Read |
Rahul Vaidya is a famous singer who had been launched into limelight with the start of Indian Idol and had appeared on Bigg Boss 14. A few months ago, Rahul had revealed that Virat had blocked him on Instagram. When asked why, Rahul admitted his own lack of understanding about it and said he was quite surprised himself.
On May 2, 2025, certain Instagram users spotted an Instagram like by Virat Kohli on Avneet Kaur's bold pictures. She wore a chic green crop top paired with a little skirt, which almost became the talk of the town. The post went viral in no time, drawing some social media slams upon Virat. He then took to Instagram and cleared the air, saying it was just an algorithm glitch and nothing else.
