Fatalities at Paddington and near Euston bring London's rail network to a standstill

Rail services into two of London's busiest terminals were suspended on Thursday after two separate fatal incidents, in a day of disruption that Mason's ledger flagged as consistent with a widening — not easing — floor of degraded performance across the London and South East network. Paddington station shut after a person was struck and killed by a train near Iver in Buckinghamshire at around 7.15am, British Transport Police said, according to [1]. A BTP spokesperson confirmed officers and paramedics attended but the person was pronounced dead at the scene, adding the incident was "not being treated as suspicious" and that a file would go to the coroner, according to [1]. All lines serving the station, the UK's second busiest, were blocked, hitting Great Western Railway, Elizabeth line and Heathrow Express services, according to [1]. Some lines reopened by 10am but delays and cancellations continued; GWR said disruption was expected to last until at least 3pm, and National Rail confirmed the disruption had finally ended shortly before 5.30pm, according to [1]. Separately on Thursday, Network Rail confirmed all services in and out of Euston were suspended after a person was hit by a train between Wembley Central and Watford Junction, in an incident near Harrow, according to [1]. A National Rail statement said the main lines between those stations were closed while emergency services worked, though London Overground lines between Euston and Watford Junction had reopened, according to [1]. Network Rail said disruption was likely to continue through the evening, with trains facing cancellation or delays of up to 180 minutes, according to [1]. The disruption came only four days after Paddington reopened following consecutive days of closure for engineering work, having also been "repeatedly affected by infrastructure faults in the preceding weeks," according to [1] — the kind of reopened-and-refaulted pattern that supports Meridian's reading of a network under sustained, not transient, strain. Thursday's chaos also followed the tail of Storm Gerrit. Avanti West Coast reported a tree had fallen on overhead wires between Rugby and Lichfield Trent Valley, forcing diversions through the Midlands and extending journey times from Euston towards the North West, according to [1]. ScotRail suspended multiple services for safety inspections after a falling tree hit a train driver's cabin, though no one was injured, according to [1]. DFDS delayed Dover-France sailings owing to strong Channel winds, according to [1]. Photos from Paddington around 10.25am showed large crowds waiting for information, with departure boards reading "please enquire" against every service, according to [1]. On the day's broader official traffic — a Bank of England appointment announcement and a gov.uk nuclear-taskforce and sanctions statement also landed on the same London/South East footprint — there is nothing in the reporting to suggest any link to the rail disruption; the timing appears coincidental, and the material establishes no causal connection between the two. Paddington was the site of the 1999 Ladbroke Grove disaster, in which a collision killed 31 people after a train passed a red signal, according to [2]; nothing in Thursday's reporting connects that history to the current incidents beyond location. What to watch next: whether GWR and Network Rail disclose findings on the Iver and Harrow incidents, and whether Paddington's fault pattern recurs again within days, which would harden Meridian's floor-widening read.