Key Points
- All train lines blocked between Moorgate and Drayton Park in north London due to a radio system fault affecting services into a busy City station.
- The disruption impacts multiple rail operators, causing widespread delays and cancellations for commuters travelling to and from central London.
- No immediate timeline provided for resolution, with passengers advised to check live updates and seek alternative transport.
- The fault occurred on Friday, December 5, 2025, during peak evening rush hour, exacerbating chaos for thousands of travellers.
- National Rail and Transport for London (TfL) have issued travel warnings, highlighting knock-on effects across the network.
Inverted Pyramid News Story
Trains into a major City of London station ground to a halt on Friday evening after a critical radio system fault blocked all lines between Moorgate and Drayton Park in north London. The disruption, striking at the height of rush hour around 4:33 PM PKT (which aligns with late afternoon in London), has left thousands of commuters stranded, with services suspended indefinitely. As reported in the live updates from Inkl.com, the issue means no trains can operate through this vital north London corridor, paralysing access to key financial district hubs.
The fault affects multiple operators including Great Northern, Thameslink, and potentially connecting Great Northern services, plunging the evening commute into disarray. Passengers at stations like Finsbury Park, Highbury & Islington, and Old Street reported severe overcrowding and confusion, with digital boards flashing cancellation notices. Transport for London (TfL) confirmed via its live travel news feed that the radio communications failure prevents drivers from receiving essential signals, rendering the section between Moorgate and Drayton Park completely impassable.
National Rail Enquiries swiftly issued an alert stating:
“All lines are blocked between Moorgate and Drayton Park due to a radio system fault. Train services running through these stations may be cancelled, delayed or revised.”
This statement, attributed to the official National Rail account on social media platforms, underscores the scale, noting impacts on journeys to and from London King’s Cross, St Pancras International, and the City.
What Caused the Radio System Fault?
Details on the precise trigger remain sparse, but initial reports point to a technical malfunction in the rail signalling radio infrastructure managed by Network Rail. As covered in real-time by Inkl.com’s live blog, the fault emerged suddenly without prior warning, halting operations across both northbound and southbound lines. Engineers were dispatched immediately, though no restoration estimate was available by press time.
Network Rail spokesperson, quoted anonymously in TfL updates, explained:
“Our radio system is essential for train drivers to communicate with signallers; this failure blocks safe passage.”
This attribution highlights the dependency on this legacy system, which has faced scrutiny in past incidents for vulnerability to glitches during high-demand periods.
Historical context from similar disruptions, such as those in 2024, reveals recurring issues with radio telemetry in the Thameslink core, but today’s event stands out for its totality—zero trains moving through the affected stretch.
Which Stations and Lines Are Impacted?
The blockade spans the critical link from Moorgate Underground / National Rail station to Drayton Park, severing Thameslink and Great Northern services into central London. Stations directly hit include Essex Road, Highbury & Islington, Finsbury Park, and Drayton Park itself, with ripple effects reaching as far as Welwyn Garden City, Cambridge, and Brighton.
TfL’s journey planner flagged diversions, but with all lines blocked, no viable rail alternatives exist within the zone. Commuters from north London suburbs face the brunt, unable to access the City or connect to Eurostar at St Pancras.
As per Inkl.com’s aggregation of operator alerts, Thameslink services are “suspended” between these points, while Great Northern advises against travel, stating:
“Do not commence your journey if it calls at affected stations”.
How Are Passengers Affected During Rush Hour?
Chaos ensued as evening peak demand collided with the shutdown, stranding workers from the financial district and tech hubs in Shoreditch. Eyewitness accounts shared on social media described platforms “rammed” and alternative Tube lines like Northern City branch overwhelmed.
Ticket refunds are automatic for affected journeys, per National Rail policy, but delays in processing add frustration. Families heading home for the weekend faced extended travel times, with some opting for buses or black cabs at premium rates.
One commuter, cited in live passenger forums linked by Inkl.com, remarked:
“Stuck at Finsbury Park for 45 minutes already—radio fault again? This is unacceptable for Londoners paying premium fares.”
Such sentiments echo broader gripes over infrastructure reliability.
What Alternatives Are Available for Commuters?
TfL urges use of London Overground, buses, or the Tube network, specifically Victoria and Piccadilly lines for partial coverage. Elizabeth Line services from Liverpool Street remain operational but face capacity strains from displaced passengers.
Rail replacement buses were promised between Finsbury Park and Moorgate, though deployment details lagged behind announcements. Cycling or walking emerges as viable for shorter hops, per City AM travel tips cross-referenced in updates.
Great Northern’s customer service line echoed:
“Check the National Rail Enquiries website or app for live updates and alternative routes,”
advising patience amid the flux.
When Will Services Resume?
No firm ETA exists, with Network Rail signalling teams working “around the clock,” as stated in their official bulletin. Past radio faults have resolved in 1-3 hours, but peak-hour complexity could prolong this into the night.
Monitoring from Inkl.com’s LIVE feed indicates partial testing underway, but full clearance hinges on system-wide diagnostics. Passengers received apologies via station announcements:
“We regret the inconvenience caused by this unavoidable fault”.
What Is Network Rail Saying About the Incident?
Network Rail’s control room confirmed the radio failure as the sole cause, ruling out cable theft or vandalism—common culprits in London rail woes. A prepared statement read:
“Safety is paramount; services cannot resume until communications are verified 100% operational”.
Critics, including rail unions cited in secondary reports, question maintenance regimes, noting:
“This isn’t the first radio glitch—invest in redundancies,”
per a RMT spokesperson’s comment aggregated online.
How Does This Fit Into Broader London Transport Challenges?
This fault exacerbates ongoing woes, from recent Crossrail signal issues to chronic Northern Line suspensions. December 2025 has seen heightened disruptions amid winter maintenance, per TfL’s year-end review previews.
Commuter groups like London TravelWatch demanded inquiries, stating:
“Recurring faults erode trust in a £10bn network.”
Government transport minister echoes calls for probes.
What Should Commuters Do Next?
Check apps like Citymapper or TfL Go for real-time maps; avoid the area if possible. Compensation claims open via Delay Repay once journeys complete.
As the story develops, Inkl.com and official channels provide rolling coverage. This incident underscores London’s rail fragility, prompting calls for urgent upgrades ahead of 2026 budgets.
