Opentraintimes 장애 기록

1. 2026년 10월 25일 오전 8:22 UTCmonitoring

   업스트림 산업 시스템과의 문제는 우리에게 많은 다른 당사자가 수신 한 기차 운동 메시지를 방지하는 것입니다.

2. 2026년 10월 25일 오후 12:13 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 14일 오후 1:57 UTCmonitoring

   엔지니어는 TRUST 및 TD 피드를 처리하는 데 문제가 발생했습니다. 데이터는 이제 다시 흐르는, 그러나 약 15 분 동안 현실 뒤에 지연 될 수있다.

2. 2026년 10월 14일 오후 4:32 UTCmonitoring

   성능 문제 persists, 그리고 우리는 데이터의 backlog를 처리하기 위해 추가 서버를 할당

3. 2026년 10월 14일 오후 5:31 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 3일 오후 1:27 UTCidentified

   맵 및 일정 성능 데이터는 인프라 문제로 인해 현재에 업데이트되지 않습니다. 엔지니어는 투자입니다.

2. 2026년 10월 3일 오후 1:37 UTCmonitoring

   이 오류는 수정되었습니다, 지도는 현재 데이터의 백 로그로 업데이트됩니다

3. 2026년 10월 3일 오후 1:46 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 13일 오후 1:56 UTCmonitoring

   Due to a server problem, maps are running up to ~1h30m behind reality. We have fixed the underlying issue and will continue to monitor until the maps are up-to-date

2. 2026년 7월 13일 오후 5:16 UTCresolved

   This incident has been resolved.

1. 2026년 5월 16일 오후 6:18 UTCmonitoring

   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. 2026년 5월 17일 오전 9:33 UTCresolved

   This incident has been resolved.

1. 2026년 4월 10일 오전 10:09 UTCresolved

   Planned maintenance on the Network Rail Open Data platform has overrun by 20 minutes. Maps will be showing outdated information.

1. 2026년 2월 16일 오전 9:39 UTCresolved

   This incident has been resolved.

2. 2026년 2월 16일 오전 9:41 UTCpostmortem

   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.

1. 2025년 8월 24일 오후 5:14 UTCidentified

   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. 2025년 8월 24일 오후 6:34 UTCmonitoring

   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. 2025년 8월 24일 오후 7:43 UTCresolved

   This incident has been resolved.

1. 2025년 6월 28일 오후 5:07 UTCinvestigating

   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. 2025년 6월 28일 오후 5:09 UTCmonitoring

   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. 2025년 6월 28일 오후 5:27 UTCresolved

   This incident has been resolved.

1. 2025년 5월 14일 오전 11:08 UTCinvestigating

   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. 2025년 5월 14일 오후 4:44 UTCresolved

   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.

1. 2025년 3월 20일 오전 11:53 UTCidentified

   Due to a system failure, we do not currently have up-to-date real time running data. We are working to restore this in the coming hours.

2. 2025년 3월 20일 오후 10:53 UTCresolved

   This incident has been resolved.

1. 2025년 2월 14일 오전 10:56 UTCmonitoring

   From around 0100 on Friday 14th February, a number of IP addresses on the same network were scraping thousands of pages on our site, causing 404 errors to be returned to users. These addresses have been blocked and the website is now operating normally.

2. 2025년 2월 14일 오후 10:01 UTCresolved

   This incident has been resolved.

1. 2024년 11월 16일 오후 1:47 UTCidentified

   Since around 1300, we have been having issues with our data feeds from Network Rail. This appears to be an industry-wide problem, and we are working to find a resolution.

2. 2024년 11월 16일 오후 3:46 UTCresolved

   This incident has been resolved.

1. 2024년 10월 7일 오전 9:43 UTCmonitoring

   One of our servers was rebooted without warning at 0938 this morning, and services did not restart as normal. We have manually restarted services on this server, and it is currently processing through a backlog of data. Maps may be showing incorrect information for the next hour.

2. 2024년 10월 7일 오전 11:35 UTCresolved

   This incident has now been resolved.

1. 2024년 9월 3일 오전 11:41 UTCidentified

   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. 2024년 9월 3일 오후 2:19 UTCmonitoring

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

3. 2024년 9월 3일 오후 5:47 UTCresolved

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

1. 2024년 9월 3일 오전 8:42 UTCinvestigating

   Engineers have identified problems with our 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. 2024년 9월 3일 오전 8:45 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2024년 9월 3일 오전 11:13 UTCresolved

   This incident is now resolved. Maps may still show incorrect data for a few hours.

1. 2024년 8월 1일 오전 6:25 UTCinvestigating

   A problem with one of our servers has resulted in a lack of rail data to all subscribers. Engineers are investigating.

2. 2024년 8월 1일 오전 6:44 UTCmonitoring

   We have identified the problem and put in place a fix. We will continue to monitor.rf

3. 2024년 8월 1일 오전 10:08 UTCresolved

   This incident has been resolved.

1. 2024년 7월 12일 오후 4:16 UTCmonitoring

   From 1640 until approximately 1715, both of our map servers were not serving up new map data due to a common fault in the code running on each server. We have not seen this error before, but will put in place a software fix in a few days to ensure this does not happen again. Maps are now working again, and no data has been lost.

2. 2024년 7월 12일 오후 9:15 UTCresolved

   This incident has been resolved.

1. 2024년 5월 23일 오후 10:06 UTCresolved

   Between 2100 and 2300, a problem with one of our internal servers prevented any TD or TRUST messages from reaching other systems. This has now been resolved.

1. 2024년 2월 20일 오후 2:07 UTCinvestigating

   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. 2024년 2월 20일 오후 4:04 UTCresolved

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