In brief
The first South Africa‑Australia Test at Durban was battered by clouds that cut hundreds of overs, sparking backlash over a new ICC rule that lets teams switch to the pink ball if night‑fall looms. The rule, introduced last week, never got used as the teams missed the chance to agree on a ball ahead of the match. Many still question whether the pink ball truly solves lighting problems, with fans noting that while it’s easier to see in lights, it’s perceived as moving too fast. Cricket’s light issues raise fresh debates about fairness, technology and the need for a more flexible, player‑centred solution.
Folks, picture a sunny morning in Durban, the score 139 ahead for Aussie, but in a split second it’s all gray and cloud‑shaded. That’s exactly what happened in the first south‑african‑Australia Test, where bad light wrenched out over 60 overs across the first three days.
Last week the International Cricket Council (ICC) added a new rule: if day‑night lights fade into the dusk, teams can *agree on the pink ball* instead of the classic red. The rule is meant to keep the game going under poor light, but it never even touched the field—no dog‑eared team chat about it.
Why the ignore?
The Proteas and Aussies didn’t flag it before the match, and the umpires had to call a halt because of globby clouds instead. So even though the rule exists, it’s still stuck in the rule‑book, unused and arguably ineffective.
The debate rages: some say the pink ball is easier to see in evening light (think day‑night matches), but critics claim it moves too fast and is easier for bowlers than batters. Others worry the team that gets the white‑light advantage is treated unfairly.
Bottom line: Durban’s clouds proved cricket’s lighting woes are still a real problem, and while a new rule is on the table, it’s time for a better communication plan between teams and umpires before the next test starts.
