Affected components
Train movement dataSchedule data
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.
Looking to track OpenTrainTimes downtime and outages?
Pingoru polls OpenTrainTimes's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when OpenTrainTimes reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track OpenTrainTimes alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
Start monitoring OpenTrainTimes for free
5 free monitors · No credit card required