OpenTrainTimes had 5 outages in the last 2 years totaling 18h 54m of downtime — averaging 0.2 incidents per month.
There were 5 OpenTrainTimes outages since February 16, 2026 totaling 18h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.
Maps and schedule performance data are not updating at present due to an infrastructure issue. Engineers are investigating.
This fault has been rectified, and maps are currently updating with the backlog of data
This incident has been resolved.
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
This incident has been resolved.
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.
This incident has been resolved.
Planned maintenance on the Network Rail Open Data platform has overrun by 20 minutes. Maps will be showing outdated information.
This incident has been resolved.
A problem relating to database corruption for the OpenTrainTimes website caused users to receive 500 errors when viewing maps or train schedules between around 2230 on 15th February and 0915 on 16th February. The root cause was corruption on a disk partition on one of our database servers hosted on some of our older infrastructure. This server and its associated infrastructure was scheduled for renewal on to a more resilient platform before April 2026, however we are bringing this forward in the light of this outage.