Resolved on February 16, 2026, affecting Train movement data and Schedule data.
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.
Affected components
Update timeline
- resolved Feb 16, 2026, 09:39 AM UTC
This incident has been resolved.
- postmortem Feb 16, 2026, 09:41 AM UTC
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.
Your product runs on more than OpenTrainTimes
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services