OpenTrainTimes incident

Real-time information degraded

Critical Resolved View vendor source →

OpenTrainTimes experienced a critical incident on May 14, 2025 affecting Network Rail Open Data feeds, lasting 2h 59m. The incident has been resolved; the full update timeline is below.

Started
May 14, 2025, 09:00 AM UTC
Resolved
May 14, 2025, 12:00 PM UTC
Duration
2h 59m
Detected by Pingoru
May 14, 2025, 09:00 AM UTC

Affected components

Network Rail Open Data feeds

Update timeline

  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.