Cricket's bad light problem persists despite new pink ball rule

Cricket has a problem that refuses to stay solved. More than 60 overs vanished from the first Test between South Africa and Australia in Durban across the opening three days, lost not to injury or dispute but to the simple fact that the sky grew too dark to play. The frustration cuts deeper this time because the sport's governing body had just introduced a potential fix—one that neither team bothered to use.

The International Cricket Council amended its playing conditions last week to permit the pink ball in Test cricket, not merely in day-night matches under lights but as a preventive measure against exactly this kind of afternoon collapse. The rule works differently than some had imagined: it does not allow mid-match ball switches when clouds roll in. Instead, teams can agree before a Test begins to use pink throughout, trading the traditional red ball for one that carries better visibility in poor light. South Africa and Australia never had that conversation before arriving in Durban.

The weather pattern that unfolded was grimly familiar to anyone who knows the city. Play began at 09:30 local time, early by design—October at Kingsmead means the sun sets shortly after six in the evening. On day one, clouds built through the afternoon. At 15:23, with only 65.2 of the scheduled 90 overs bowled, the umpires called stumps. The players did not return. Day two stretched slightly longer, until 16:25, but still finished 35 minutes before it needed to. Day three ended at 16:31. The pattern repeated: hot sun in the morning, then a sea breeze rolling in from the coast, humidity climbing, clouds thickening and lowering as the afternoon wore on and temperatures fell.

Shaun Pollock, the former South African bowler who sat on the ICC committee recommending the pink ball change, sees a stigma at work. Players and teams resist the pink ball not because of what data shows but because of what they believe—or what they fear others will believe. "They say it moves too much," Pollock said. The ball tracking evidence does not support this. What does exist is a real pattern: batters average lower in the evening sessions of day-night matches, and some have spoken about difficulty seeing the pink ball. Australia, having played in 15 of cricket's 23 day-night Tests, has built an undeniable advantage. Mitchell Starc alone has taken 89 wickets in pink-ball cricket. No team wants to face that edge if they can avoid it.

The deeper tension sits unresolved. Vernon Philander, another former South African bowler, has suggested the ICC simply switch balls when light deteriorates, letting umpires make the call rather than leaving it to team agreement. But that raises its own problem: does one side gain an unfair advantage by suddenly playing under different conditions? If Australia had been forced to continue batting with a pink ball after building momentum with red, would the outcome have shifted? The question contains its own answer, which is why teams hesitate.

Cricket stands at a choice it has not yet made. It can enforce the pink ball as a standard tool when conditions warrant it, removing the decision from players and captains entirely. Or it can respect the autonomy of teams to choose their equipment, accepting that some Tests will lose overs to darkness because neither side wanted to risk the unknown. In Durban, the sport chose the latter. Sixty overs of Test cricket—the kind of passage that can reshape a match, that can define a series—simply did not happen. The rule existed. The solution was available. Neither team reached for it.