Ahmedabad falls. Tilak 101 off 45. And suddenly only two fortresses stand.

Forty-eight hours ago this blog ran a piece called "IPL 2026 Week 3 — the week the fortresses fell." It argued that Wankhede and Chinnaswamy had taken their first chips, and that three home fortresses remained untouched: Ahmedabad, Chepauk, and Hyderabad. Those were the venues where the hosts had still not lost a match this season.

Now it is two.

MI were 44 for 3. Then Tilak happened.

Here is the part about a 99-run win that nobody remembers after the scoreboard lights go off — the winning side was in trouble. Mumbai walked out, Quinton de Kock edged Kagiso Rabada to end up caught and bowled, Danish Malewar was trapped lbw by the same bowler, and Surya Kumar Yadav was bowled for 15. Mumbai Indians were 44 for 3 after five and a half overs at what is supposed to be the most composed bowling side's home ground.

In the dressing room I used to play in, this is the point at which the match is reset. The captain walks down the order, the batters at the crease take five balls to remind themselves what the surface is doing, and the new batter at the other end has a decision to make — consolidate or attack. Tilak Varma chose neither. He chose something harder: play properly, and accept the cost of whatever he tried.

Naman Dhir got 45 off 32 at the other end, the kind of innings that buys a partner time. The fourth wicket partnership was 52. Dhir fell at 96 for 4 in the 12th over. Mumbai still needed 104 from the last 45 balls against a GT attack that had held them to 44 in the first 33.

Seven sixes. Let that sit. On an Ahmedabad surface in April, against Rashid Khan and Kagiso Rabada and Prasidh Krishna, one batter hit seven sixes in forty-five balls. Rashid went for 31 off 4 with zero wickets — his first wicketless spell at home this season. Prasidh's last two overs went for 34. Tilak took them apart with the shots that only a batter who has decided the surface will do what he tells it to do can play.

A 99-run margin is not what the winning side did. It is what the losing side failed to do in response. But tonight both things were true at the same time — one batter scored like the pitch did not exist, and one bowling attack made sure the chase never had a second over.

— Priya Menon

The first ball set the tone

GT's chase ended in the first over. Jasprit Bumrah running in for the first ball of the innings. Sai Sudharsan caught behind the wicket. Nought off one. At Ahmedabad, the team whose batting is built around Sudharsan getting GT through the powerplay had their opener back in the dugout before the first over was done.

Two balls later in the second over Jos Buttler was lbw to Hardik Pandya for 5. Two overs after that Shubman Gill nicked Ashwani Kumar to a Naman Dhir catch for 14. Gujarat Titans, the team that has made calm chasing its defining quality this season, were 40 for 3 in 4.4 overs.

Washington Sundar played the one innings of real fight — 26 off 17 with five fours. He fell to Mitchell Santner for a ball well bowled. Then everything collapsed.

Ashwani Kumar's four-over demolition

Somebody is going to write about Ashwani Kumar tomorrow. The left-arm quick, still new to this level of cricket, bowled four overs for 24 runs and took four wickets. Gill first. Then Tewatia. Then Shahrukh Khan for 17 — the only GT batter who looked like he might take the chase back towards a respectable finish. Then Rashid Khan for 4. A four-wicket haul at Ahmedabad against a batting order that includes Gill, Buttler, Sundar, and Phillips is not a career-defining night. But it is the kind of performance you put at the top of your highlight reel and do not take down.

Am Ghazanfar, the off-spinner, finished it with 2 for 17 in 2.5 overs. Mitchell Santner had Sundar and Phillips in the same over — 7.4, the ball that ended any serious GT intent.

None of the MI bowling lines are vanity. Bumrah 3-0-15-1 (the first-ball wicket plus later pressure). Hardik 1-0-18-1 (Buttler's head). Santner 3-0-16-2. Krish Bhagat 2-0-10-0, a quiet, tight spell that gave Santner and Ghazanfar the field they needed. The attack that leaked against Punjab at Wankhede three days ago did not leak tonight.

CM AI and what we called

Here is the honest entry. Our pre-toss social feed did not carry a CM AI prediction for this match. It is the first IPL 2026 fixture we have let pass without a pre-toss call — a result of the ai_prediction pipeline not being wired for the ad-hoc reschedule the fixture list quietly moved through this week. We noticed. We are fixing it. And we are publishing the fact that we missed it because cricketmind.ai/accuracy only works if every match is on the record, including the ones where the record reads "no call made."

The fix lands this week. No match goes uncalled from here on.

What this means for the season

Three fortresses on April 17. Two on April 19. Chepauk and Hyderabad are the two grounds in IPL 2026 where the home side has not yet lost. CSK are at Chepauk next week. SRH are at Rajiv Gandhi. Both face opposition that has already read the surface and will have MI's game plan in mind when they travel.

For Gujarat Titans, the question is sharper than for most teams that lose by 99 runs. Two weeks ago this side looked like a genuine title contender built around calm, composure, and an attack that suffocates chases. Tonight all three of those attributes broke at the same time. Gill's batting has been quiet for four matches now. Rashid has not taken a wicket in his last two. Sudharsan's first-ball dismissal is the kind of moment that will sit in a young opener's head longer than anyone in a press conference will admit. One bad night does not overturn a squad. But a 99-run home loss where both the batting and the bowling gave way in the same evening is not one bad night. It is a set of questions the team has to answer in the next match.

For Mumbai Indians, this was a correction. The loss to Punjab at Wankhede three days ago was a real dent in the home-fortress story. Tonight was the response. Not because they went home and put their house in order — they did not go home. They went to Ahmedabad, to the toughest home ground in the competition, and won by 99.

Mumbai's title credentials are back in the conversation. They travel again this week.

Priya Menon Senior Match Analyst CricketMind AI