OpenTrainTimes incident

Real-time information degraded

Resolved after 3 hours 4 minutes, affecting Network Rail Open Data feeds, on February 20, 2024.

resolved Feb 20, 2024, 04:04 PM UTC

Data is now being received as normal. Maps may show erroneous data for several hours for infrequently-occupied train describer berths.

Started
Feb 20, 2024, 01:00 PM UTC
Resolved
Feb 20, 2024, 04:04 PM UTC
Duration
3h 4m
Detected by Pingoru
Feb 20, 2024, 01:00 PM UTC

Affected components

Network Rail Open Data feeds

Update timeline

  1. investigating Feb 20, 2024, 02:07 PM 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 Feb 20, 2024, 04:04 PM UTC

    Data is now being received as normal. Maps may show erroneous data for several hours for infrequently-occupied train describer berths.

Your product runs on more than OpenTrainTimes

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →