Trespass incident hits Greater Anglia lines through Meridian Water

Services on Greater Anglia's core London routes were disrupted on 12 June after a trespass incident between Northumberland Park and Meridian Water, according to National Rail's incident report [2]. The disruption affected trains between London Liverpool Street and Stratford, and Brimsdown, with knock-on effects on the wider Greater Anglia network [2]. The routes hit included Greater Anglia services between London Liverpool Street and Hertford East, Cambridge and Cambridge North, and between Stratford and Bishops Stortford, as well as the Stansted Express between Liverpool Street and Stansted Airport [2]. National Rail confirmed trains were "now running normally" following the incident, without giving a timeframe for how long the disruption lasted [2]. Meridian Water station itself carries some standing operational quirks that compound any disruption there. It is classified as a category A station under the Office of Rail and Road's station classification system [1]. Passengers are advised to travel in the front seven coaches of any train, a restriction that applies specifically to Greater Anglia's 10-coach services because the doors on the rear three coaches do not open at the platform [1]. That is a permanent feature of the station, not a fault caused by the trespass incident, but it is worth flagging to Wayne because it means even a routine service running to this stop carries an added constraint that could compound delays or crowding if disruption recurs. This incident sits inside a broader pattern flagged by the estate's own monitoring instruments: a cluster of London-anchored rail disruption and performance data showing multiple termini running at sub-65% on-time performance, alongside several routes closed and reopened in short order [Trigger]. Meridian's own rotating-station note treats this as consistent with routine but wide-reaching Bank-Holiday-tail strain across the network, rather than anything exceptional [Trigger]. The Meridian Water trespass incident fits that pattern as one node in a wider set of service interruptions rather than a standalone event. A second item was tagged alongside this cluster by the same monitoring system: an unrelated gov.uk entry sharing a population statistic — 14.08 million people living within 50km, a marker of Greater London's exposure — attached to what is described as a strike-off notice [Trigger]. There is nothing in the material provided that establishes any substantive connection between that gov.uk item and the Meridian Water rail disruption beyond this shared population tag. This reads as a coincidental co-tagging by the monitoring system rather than a genuine link, and Wayne should treat it as noise rather than signal until further reporting says otherwise. What isn't established here: the duration of the Meridian Water disruption, the cause or outcome of the trespass incident itself, and whether the wider termini punctuality cluster stems from a common cause or is simply several unrelated strains landing on the network at once. What to watch next: whether National Rail or Greater Anglia publish a fuller incident report on the Meridian Water trespass, and whether the sub-65% punctuality readings at London termini persist beyond this Bank Holiday period or resolve as isolated events.