[status] Monitoring: We are now receiving TRUST messages, although any data produced between 1712 and 1927 has not been received. We will monitor for the next hour before closing this incident. https://t.co/Yuzu0xQAnh
[status] Identified: We have not received any TRUST data from Network Rail since around 1712 today, nor have a number of other industry systems. We understand that there is a widespread outage. Maps will still be functioning. https://t.co/5XlTAtSDSg
[status] Investigating: Automated monitoring has detected a total loss of data from the Network Rail Open Data platform to our servers.
As a result, train movements are not updating on maps and train schedules will not show tracking … https://t.co/ljbxIvwh7o
[status] Resolved: This issue has now been resolved. We are awaiting a response from CACI, who manage the system on behalf of Network Rail, and we have also made an FOI request to help everyone understand the criticality of Open Data… https://t.co/5Dn60lO5wg
[status] Investigating: Engineers have identified high latency on our real-time feeds from the Network Rail Open Data platform. As a result, the real-time components of the website will be showing out-of-date or missing data. https://t.co/UMuk2i8rlH
[status] Monitoring: From around 0100 on Friday 14th February, a number of IP addresses on the same network were scraping thousands of pages on our site, causing 404 errors to be returned to users.
These addresses have been blocked a… https://t.co/P3dJVudGdo
[status] Identified: Since around 1300, we have been having issues with our data feeds from Network Rail. This appears to be an industry-wide problem, and we are working to find a resolution. https://t.co/6ahStr3r1n
[status] Identified: Due to a long-standing problem with the BST->GMT transition, train movement data is not showing correctly on the website. Maps are unaffected. https://t.co/H1YlVqzbHs
[status] Monitoring: One of our servers was rebooted without warning at 0938 this morning, and services did not restart as normal. We have manually restarted services on this server, and it is currently processing through a backlog o… https://t.co/j16EIogeJe
[status] Investigating: Engineers have identified problems with our feeds from the Network Rail Open Data platform. As a result, the real-time components of the website will be showing out-of-date or missing data. https://t.co/FH4RFSdpoy
[status] Investigating: A problem with one of our servers has resulted in a lack of rail data to all subscribers. Engineers are investigating. https://t.co/QxjvxqAQAX
[status] Monitoring: From 1640 until approximately 1715, both of our map servers were not serving up new map data due to a common fault in the code running on each server. We have not seen this error before, but will put in place a s… https://t.co/RPnfyNV7B1
@AliceConsortium AWS require we use a CNAME to refer to the load balancer for the site, but RFC1034 disallows a CNAME at the domain apex. There are solutions available but nothing that suits our infrastructure at the moment
Some users have reported that the maps on our site are not loading at the moment - we're unable to reproduce this problem and everything looks OK. Please comment here if you're affected
@EWSTrains Yes - these will be updated in due course. We don't make any money from the public site, and we have to prioritise paid work so we can pay the bills and keep the site free!
Good use of bi-directional signalling between Burgess Hill and Preston Park for some GTR services due to a landslip near Hassocks
https://t.co/kAPTkLHwsN