История сбоев Opentraintimes

1. 25 октября 2026 г. в 08:22 UTCmonitoring

   Проблема с вышестоящей отраслевой системой заключается в недопущении получения сообщений о движении поездов нами и многими другими сторонами.

2. 25 октября 2026 г. в 12:13 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 14 октября 2026 г. в 13:57 UTCmonitoring

   Инженеры были предупреждены о проблеме с обработкой наших каналов TRUST и TD, вызванной проблемой сервера на нашей стороне. Данные сейчас снова текут, но могут отставать от реальности примерно на 15 минут.

2. 14 октября 2026 г. в 16:32 UTCmonitoring

   Проблема производительности сохраняется, и мы назначили дополнительные серверы для обработки отставания данных

3. 14 октября 2026 г. в 17:31 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 3 октября 2026 г. в 13:27 UTCidentified

   Карты и данные о производительности графика в настоящее время не обновляются из-за проблем с инфраструктурой. Инженеры ведут расследование.

2. 3 октября 2026 г. в 13:37 UTCmonitoring

   Эта ошибка была исправлена, и карты в настоящее время обновляются с отставанием данных

3. 3 октября 2026 г. в 13:46 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 13 июля 2026 г. в 13: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. 13 июля 2026 г. в 17:16 UTCresolved

   This incident has been resolved.

1. 16 мая 2026 г. в 18: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. 17 мая 2026 г. в 09:33 UTCresolved

   This incident has been resolved.

1. 10 апреля 2026 г. в 10:09 UTCresolved

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

1. 16 февраля 2026 г. в 09:39 UTCresolved

   This incident has been resolved.

2. 16 февраля 2026 г. в 09: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. 24 августа 2025 г. в 17: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. 24 августа 2025 г. в 18: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. 24 августа 2025 г. в 19:43 UTCresolved

   This incident has been resolved.

1. 28 июня 2025 г. в 17: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. 28 июня 2025 г. в 17: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. 28 июня 2025 г. в 17:27 UTCresolved

   This incident has been resolved.

1. 14 мая 2025 г. в 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. 14 мая 2025 г. в 16: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. 20 марта 2025 г. в 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. 20 марта 2025 г. в 22:53 UTCresolved

   This incident has been resolved.

1. 14 февраля 2025 г. в 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. 14 февраля 2025 г. в 22:01 UTCresolved

   This incident has been resolved.

1. 16 ноября 2024 г. в 13: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. 16 ноября 2024 г. в 15:46 UTCresolved

   This incident has been resolved.

1. 7 октября 2024 г. в 09: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. 7 октября 2024 г. в 11:35 UTCresolved

   This incident has now been resolved.

1. 3 сентября 2024 г. в 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. 3 сентября 2024 г. в 14:19 UTCmonitoring

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

3. 3 сентября 2024 г. в 17: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. 3 сентября 2024 г. в 08: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. 3 сентября 2024 г. в 08:45 UTCidentified

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

3. 3 сентября 2024 г. в 11:13 UTCresolved

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

1. 1 августа 2024 г. в 06:25 UTCinvestigating

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

2. 1 августа 2024 г. в 06:44 UTCmonitoring

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

3. 1 августа 2024 г. в 10:08 UTCresolved

   This incident has been resolved.

1. 12 июля 2024 г. в 16: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. 12 июля 2024 г. в 21:15 UTCresolved

   This incident has been resolved.

1. 23 мая 2024 г. в 22: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. 20 февраля 2024 г. в 14: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. 20 февраля 2024 г. в 16:04 UTCresolved

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