Trackside fire shuts London Victoria services after chaos at Clapham Junction

Wayne's monitoring instruments flagged major disruption in the Clapham Junction area on 31 July, covering Gatwick Express services to and from London Victoria, London Overground between Stratford/Dalston Junction and Clapham Junction, and all Southern services to and from London Victoria. The trigger has been checked against National Rail and Southern Railway's own service updates, and the picture is now clear. According to Southern Railway's service update page, the cause was a fire next to the track in the Clapham Junction area, which disrupted multiple lines and led to trains being cancelled, delayed by up to 60 minutes, diverted or revised [2]. The fire caused damage to signalling equipment on the route, and Southern said no services were able to run to or from London Victoria until repairs were carried out [2]. Passengers were advised to use alternative Thameslink services via London Bridge and to allow at least 60 minutes' extra journey time [2]. Southern also confirmed that London Overground trains between Dalston Junction and Clapham Junction were being diverted to and from Battersea Park and would not call at Clapham Junction during the disruption, matching the Overground element flagged by Wayne's instruments [2]. Passengers holding tickets for the affected routes were told they could use listed alternative services at no extra cost, and that they may be entitled to compensation for delays, provided they retain their tickets and note journey details [2]. Southern's update also included a safety notice relevant to anyone caught up in the incident: passengers on trains delayed between stations were told to remain in place, listen to announcements or speak to staff, and not to leave the train unless instructed, given the hazards of a live third rail and moving trains in the area [2]. Separately, South Western Railway services were confirmed as running normally throughout, indicating the disruption was contained to the Southern, Gatwick Express and Overground routes into Victoria rather than affecting the wider Clapham Junction interchange [2]. Critically, National Rail's incident page for Clapham Junction states plainly that "disruption following a number of incidents in the Clapham Junction area today has now ended" [1]. That closes out the event: the fire has been dealt with, signalling repaired or restored sufficiently for services to resume, and the major disruption that triggered this alert is over. One thing worth flagging for the record: the Southern service-updates source text also contained unrelated engineering-work notices for Tonbridge, and for the Tulse Hill–Sutton line via Mitcham Junction [2]. These are separate, planned works and not connected to today's fire-related incident — they're noted here only because they appeared in the same fetched page, not because they bear on Wayne's Clapham Junction trigger. What to watch next: whether Southern or Network Rail publish a follow-up on the cause of the trackside fire, and whether any compensation claims process opens for passengers delayed on the affected routes today.