Thameslink disruption today and inaccurate departure information

[AndyY]

1. Massive disruption this morning (http://www.nationalrail.co.uk/service_disruptions/163477.aspx). The National Rail website says that 06:47 from ELS was running, but when I got to the station, I was told by staff that no trains would be running for at least the next 90 minutes.

This is the second signalling problem in 2 weeks (I understand that last time was because of a fire). I wonder why the line has so many problems with signalling and overhead power supply?

2. Last night 21:00 northbound from KTN was delayed by about 6-7 minutes. The departure board said On Time, then the train completely disappeared off the board with no announcement! I was about to phone 03457484950 when the train turned up. No announcement or apology on train re: late running either.

I wonder why the departure boards are so unreliable of late.

 

[infobleep]

Trains on the Sutton loop were showing as on time despite not having left Bedford. Quiet a few cancellations. The only saving grace at times was the Southern services to London Bridge. However they only run in one direction in the morning and when they stopped.... Nothing for oce am hour in either and direction. Some trains did run but they either her ran fast or terminated / started short at Wimbledon.

No mention about being able to use local buses either, bar some that ran around the elephant and catsle area.

 

[maniacmartin]

This morning, RealTimeTrains was showing a message that some real-time data sources were down or disconnected from them, so perhaps the problem with the departure boards was a national issue and not specific to Thameslink on this occasion?

 

[JB_B]

As soon as you have anything more than the slightest disruption GTR's passenger information becomes more or less useless. Departure boards fill up with services which are either indefinitely delayed or miraculously still "on time" hours after their expected departure. Presumably the system requires a significant amount of manual input which GTR are unwilling or unable to resource.

 

[Class 466]

There's an ongoing issue with reporting at the moment - started yesterday (as seen from this photo!)

 

[philjo]

This morning, RealTimeTrains was showing a message that some real-time data sources were down or disconnected from them, so perhaps the problem with the departure boards was a national issue and not specific to Thameslink on this occasion?

One of the GN services I was intending to catch this morning was cancelled but RTT was till showing it as on time.

I did get the text message alert of the cancellation though (from journeycheck)