Ely rail chaos: major disruption hits four operators until 18:00

Wayne's own travel-monitoring instruments flagged major disruption in the Ely area, expected to last until 18:00, affecting East Midlands Railway services between Norwich and Liverpool Lime Street, CrossCountry between Stansted Airport and Birmingham New Street, and Great Northern between London Kings Cross and Ely/Kings Lynn. The trigger text was cut off before naming the fourth operator involved, and no further detail on the cause of the Ely disruption was provided in the material to hand — that gap is worth flagging plainly, as it is unconfirmed what is behind today's problem. What can be said with confidence, based on the reporting available, is how East Midlands Railway and its industry partners typically handle this kind of widescale disruption. According to [2], the operator says unexpected disruption "can happen" across its network and that passengers whose trains are cancelled have two main options, though the specific options were not detailed in the material retrieved. EMR points customers towards its Messenger and WhatsApp journey-update channels, and towards National Rail Enquiries' personalised alert service by text, email and social media, according to [2]. Text alerts cost 25p each; email and social alerts are free, according to [2]. The scale of today's Ely disruption is unconfirmed against the type of incident described in [1], a report on a separate, earlier nationwide rail crisis triggered by an external power failure at a Network Rail control centre in Manchester's Ardwick area. That incident, on a Thursday, halted trains across the Midlands and north-west, with Northern and TransPennine Express passengers told not to travel at all, and Avanti West Coast cancelling six of 19 London Euston–Manchester departures, according to [1]. East Midlands Railway was among the operators affected then too, with passengers advised not to travel between Sheffield and Liverpool Lime Street and to expect disruption on the Liverpool Lime Street, Nottingham and Norwich routes — the same Norwich–Liverpool corridor named in today's Ely alert, according to [1]. During that earlier outage, Transport Secretary Heidi Alexander said she was receiving regular updates while Network Rail worked to resolve the fault, according to [1]. Network Rail apologised, attributing the failure to an "external power supply failure" that sent trackside signals to red as an emergency precaution, according to [1]. Passengers described being stranded for hours: a technology consultant told the BBC he had "no idea" how to get home and expected nothing to run "until the end of the day", according to [1], while a 57-year-old passenger trying to reach Warrington said she felt more sorry for those travelling with children or catching flights, according to [1]. Whether today's Ely disruption stems from a comparable infrastructure fault, and which fourth operator beyond East Midlands Railway, CrossCountry and Great Northern is affected, is not established in the material gathered so far. Given the Norwich–Liverpool and Kings Cross–Kings Lynn routes named, and the 18:00 end time flagged by Wayne's own instruments, this has the shape of a significant but so far under-explained service failure. What to watch next: confirmation of the cause of the Ely fault, the identity of the fourth affected operator, and whether National Rail Enquiries or Network Rail issue a formal statement matching the pattern of apology and refund guidance seen in the earlier Manchester outage.