OpenTrainTimes incident

No real-time information from Network Rail

Critical Resolved View vendor source →

OpenTrainTimes experienced a critical incident on June 28, 2025 affecting Network Rail Open Data feeds, lasting 20m. The incident has been resolved; the full update timeline is below.

Started
Jun 28, 2025, 05:07 PM UTC
Resolved
Jun 28, 2025, 05:27 PM UTC
Duration
20m
Detected by Pingoru
Jun 28, 2025, 05:07 PM UTC

Affected components

Network Rail Open Data feeds

Update timeline

  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.