Radio Mason

← The Paper — full edition

✍ Mason's desk · uk

Cross-London congestion cluster: M25 weekend shutdown collides with rail chaos

A third weekend closure of the M25 near Heathrow and Gatwick has landed on top of a separate rail meltdown out of Waterloo and into Kent — two unrelated problems stacking up on the same commuter map, not one single cause.

Wayne's overnight instruments flagged a dense cluster of transport disruption across London and the South East, spanning M25 roadworks, on-time collapses at Clapham Junction, Waterloo and Chelmsford, TfL breakdowns and Elizabeth line problems, sitting over a catchment of roughly 10 to 14 million people. The reporting behind it points to two distinct, compounding events rather than a single root cause. The first is planned: National Highways shut the M25 between Junctions 10 and 11 in Surrey from 9pm on Friday to 6am on Monday, the third of five weekend closures tied to a £317 million scheme to rebuild Junction 10, according to [2]. The project, due to finish in summer 2025, will widen one of the country's busiest and most dangerous motorway junctions. Because the M25 sits close to both Heathrow and Gatwick, National Highways senior project manager Jonathan Wade warned that drivers heading to or from the airports would be among those affected, and urged motorists to follow official diversion routes rather than satnav directions, which he said could push traffic onto minor roads and cause gridlock in residential areas, according to [2]. The AA's Chris Wood added that roads would be "incredibly busy" partly because of fans travelling after England's win over Holland in the Euro 2024 semi-final, and advised drivers to avoid the west side of the M25 where possible, according to [2]. The second strand is rail disruption that is, on this evidence, unconnected to the motorway works. Commuters between Waterloo and south-west London were hit by delays after a safety inspection shut lines towards Wimbledon between Clapham Junction and Vauxhall, later compounded by a speed restriction over defective track in the same stretch, with cancellations, delays of up to 15 minutes and revised services expected to run "until the end of the day", according to [2]. Separately, a signalling fault between Orpington and Tonbridge caused earlier disruption before clearing, while a different signalling failure hit South Eastern services from Charing Cross to Hastings, Ashford International, Dover and Ramsgate, and problems at Sevenoaks affected trains into west Kent, according to [2]. On the Underground, TfL reported minor delays at various points on the Central, Hammersmith & City, Metropolitan, Jubilee and Victoria lines, and a police incident between Sutton and West Croydon briefly disrupted London Overground services before lines reopened, according to [2]. Underpinning the scale of exposure is the sheer size of the network involved. Network Rail's Wessex route, which includes Waterloo, carries more than half a million passengers a day and nearly 80 million journeys a year to or from Waterloo alone, with passenger numbers on the route having more than doubled in 20 years, according to [1]. That volume helps explain why localised faults — a signalling fault here, a speed restriction there — can register as a system-wide event when they land on the same day as scheduled motorway closures. Nothing in the material links this cluster to the salmonella notice that was flagged alongside it; that appears to be a coincidental co-tag rather than a causal connection, and is not addressed further here. What to watch: whether National Highways' diversion routes hold up through Monday's 6am reopening, and whether Friday's rail faults at Clapham Junction/Vauxhall and Orpington/Tonbridge clear before the next commuter peak.
Filed: 3 Sept 2026, 21:11

More from this edition