OpenTrainTimes Outage History

OpenTrainTimes is up right now

Pingoru has recorded 51 incidents for OpenTrainTimes: 6 in the last 12 months and 2 in the last 90 days.

Source: status.opentraintimes.com

51incidents recorded
6last 12 months
2last 90 days
4 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking OpenTrainTimes in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202610 of 720 (0%)
May 2026115 of 744 (2%)
June 202600 of 720 (0%)
July 202613 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202624 of 509 (1%)

Incidents, newest first

Minor October 14, 2026 TD and TRUST feed issue 3h 33m Train movement data, Map data

Started Oct 14, 2026, 01:57 PM UTC· resolved Oct 14, 2026, 05:31 PM UTC

  1. monitoring Oct 14, 2026, 01:57 PM UTC

    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.

  2. monitoring Oct 14, 2026, 04:32 PM UTC

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

  3. resolved Oct 14, 2026, 05:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 3, 2026 Degraded real-time information 19m Train movement data, Map data

Started Oct 03, 2026, 01:27 PM UTC· resolved Oct 03, 2026, 01:46 PM UTC

  1. identified Oct 03, 2026, 01:27 PM UTC

    Maps and schedule performance data are not updating at present due to an infrastructure issue. Engineers are investigating.

  2. monitoring Oct 03, 2026, 01:37 PM UTC

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

  3. resolved Oct 03, 2026, 01:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 13, 2026 Map lag 3h 20m Map data

Started Jul 13, 2026, 01:56 PM UTC· resolved Jul 13, 2026, 05:16 PM UTC

  1. monitoring Jul 13, 2026, 01:56 PM UTC

    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

  2. resolved Jul 13, 2026, 05:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 16, 2026 404 errors due to excessive traffic 15h 15m Schedule data

Started May 16, 2026, 06:18 PM UTC· resolved May 17, 2026, 09:33 AM UTC

  1. monitoring May 16, 2026, 06:18 PM UTC

    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.

  2. resolved May 17, 2026, 09:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 10, 2026 Overrunning maintenance work on Open Data platform – Network Rail Open Data feeds

Started Apr 10, 2026, 09:51 AM UTC· resolved Apr 10, 2026, 09:51 AM UTC

  1. resolved Apr 10, 2026, 10:09 AM UTC

    Planned maintenance on the Network Rail Open Data platform has overrun by 20 minutes. Maps will be showing outdated information.

Read the full incident report →

Critical February 16, 2026 Website down – Train movement data, Schedule data

Started Feb 16, 2026, 09:20 AM UTC· resolved Feb 16, 2026, 09:20 AM UTC

  1. resolved Feb 16, 2026, 09:39 AM UTC

    This incident has been resolved.

  2. 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.

Read the full incident report →

Critical August 24, 2025 TRUST feed outage 3h 31m TRUST Feed

Started Aug 24, 2025, 04:12 PM UTC· resolved Aug 24, 2025, 07:43 PM UTC

  1. identified Aug 24, 2025, 05:14 PM UTC

    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.

  2. monitoring Aug 24, 2025, 06:34 PM UTC

    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.

  3. resolved Aug 24, 2025, 07:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 28, 2025 No real-time information from Network Rail 20m Network Rail Open Data feeds

Started Jun 28, 2025, 05:07 PM UTC· resolved Jun 28, 2025, 05:27 PM UTC

  1. investigating Jun 28, 2025, 05:07 PM UTC

    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 in real-time.

  2. monitoring Jun 28, 2025, 05:09 PM UTC

    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.

  3. resolved Jun 28, 2025, 05:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 14, 2025 Real-time information degraded 2h 59m Network Rail Open Data feeds

Started May 14, 2025, 09:00 AM UTC· resolved May 14, 2025, 12:00 PM UTC

  1. investigating May 14, 2025, 11:08 AM UTC

    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.

  2. resolved May 14, 2025, 04:44 PM UTC

    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 systems.

Read the full incident report →

Major March 20, 2025 Missing live schedule data 10h 59m Schedule data

Started Mar 20, 2025, 11:53 AM UTC· resolved Mar 20, 2025, 10:53 PM UTC

  1. identified Mar 20, 2025, 11:53 AM UTC

    Due to a system failure, we do not currently have up-to-date real time running data. We are working to restore this in the coming hours.

  2. resolved Mar 20, 2025, 10:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 16, 2024 Disruption to incoming data feeds 1h 59m TRUST Feed, TD Feed

Started Nov 16, 2024, 01:47 PM UTC· resolved Nov 16, 2024, 03:46 PM UTC

  1. identified Nov 16, 2024, 01:47 PM UTC

    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.

  2. resolved Nov 16, 2024, 03:46 PM UTC

    This incident has been resolved.

Read the full incident report →