OpenTrainTimes Outage History

Engineers have been alerted to a problem with processing our TRUST and TD feeds, caused by a server issue on our side. Data is now flowing again, but may lag behind reality for about 15 minutes.

The performance issue persists, and we have assigned additional servers to process the backlog of data

This fault has been rectified, and maps are currently updating with the backlog of data

Due to a server problem, maps are running up to ~1h30m behind reality. We have fixed the underlying issue and will continue to monitor until the maps are up-to-date

Over the past weeks, we have been having a chronic issue with bots (likely AI bots) scraping content on our website at a rate far exceeding even our regular peak traffic levels. This results in occasional 404 errors when viewing pages on the site. We are working to limit this traffic and have put additional mitigations in place.

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.

We are now receiving real-time data, although there is a gap of several minutes between 1801 and 1807 where there is limited data. Maps will therefore be showing incorrect data until a train passes through each berth.