OpenTrainTimes incident

Real-time information degraded

Resolved after 6 hours 6 minutes, affecting Network Rail Open Data feeds, on September 3, 2024.

resolved Sep 03, 2024, 05:47 PM UTC

Feeds have been stable for some hours and we are closing this incident. Our supplier is still working on a root cause analysis.

Started
Sep 03, 2024, 11:41 AM UTC
Resolved
Sep 03, 2024, 05:47 PM UTC
Duration
6h 6m
Detected by Pingoru
Sep 03, 2024, 11:41 AM UTC

Affected components

Network Rail Open Data feeds

Update timeline

  1. identified Sep 03, 2024, 11:41 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. This is a repeat of the incident this morning.

  2. monitoring Sep 03, 2024, 02:19 PM UTC

    Latency has been stable since 1430 - we will keep monitoring until the end of the evening peak

  3. resolved Sep 03, 2024, 05:47 PM UTC

    Feeds have been stable for some hours and we are closing this incident. Our supplier is still working on a root cause analysis.

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 →