OpenTrainTimes Outage History

OpenTrainTimes degraded View live status →

OpenTrainTimes had 5 outages in the last 2 years totaling 19h 7m of downtime — averaging 0.2 incidents per month.

There were 5 OpenTrainTimes outages since June 28, 2025 totaling 19h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.opentraintimes.com

Minor May 16, 2026

404 errors due to excessive traffic

Detected by Pingoru
May 16, 2026, 06:18 PM UTC
Resolved
May 17, 2026, 09:33 AM UTC
Duration
15h 15m
Affected: Schedule data
Timeline · 2 updates
  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

Detected by Pingoru
Apr 10, 2026, 09:51 AM UTC
Resolved
Apr 10, 2026, 09:51 AM UTC
Duration
—
Affected: Network Rail Open Data feeds
Timeline · 1 update
  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

Detected by Pingoru
Feb 16, 2026, 09:20 AM UTC
Resolved
Feb 16, 2026, 09:20 AM UTC
Duration
—
Affected: Train movement dataSchedule data
Timeline · 2 updates
  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

Detected by Pingoru
Aug 24, 2025, 04:12 PM UTC
Resolved
Aug 24, 2025, 07:43 PM UTC
Duration
3h 31m
Affected: TRUST Feed
Timeline · 3 updates
  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

Detected by Pingoru
Jun 28, 2025, 05:07 PM UTC
Resolved
Jun 28, 2025, 05:27 PM UTC
Duration
20m
Affected: Network Rail Open Data feeds
Timeline · 3 updates
  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 →