Mistral Data Outage History

Started Oct 14, 2026, 08:32 AM UTC· resolved Oct 14, 2026, 11:19 AM UTC

1. investigating Oct 14, 2026, 08:32 AM UTC

   We are aware of an issue affecting the availability of crew allocation from an upstream system. As a result, crew data for today's services may be unavailable or incomplete. We are actively working with the supplier to investigate and resolve the issue as quickly as possible. Further updates will be provided as more information becomes available. We apologise for any inconvenience caused and thank you for your patience.

2. resolved Oct 14, 2026, 11:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 15, 2026, 08:41 AM UTC· resolved Sep 21, 2026, 04:03 PM UTC

1. investigating Sep 15, 2026, 08:41 AM UTC

   This is a test banner

Read the full incident report →

Started Aug 11, 2026, 02:47 PM UTC· resolved Aug 14, 2026, 03:57 PM UTC

1. monitoring Aug 11, 2026, 02:47 PM UTC

   The issue impacting data completeness from Darwin is now resolved. We're working with RDG to understand root cause and permanent resolution

2. resolved Aug 14, 2026, 03:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 17, 2026, 08:17 AM UTC· resolved Jul 17, 2026, 11:36 AM UTC

1. investigating Jul 17, 2026, 08:17 AM UTC

   We are investigation an issues with LINX allocations data. We are working with the supplier to rectify this issue.

2. identified Jul 17, 2026, 08:28 AM UTC

   We are currently experiencing an issue affecting the Stock Allocations data feed from LINX. The disruption is due to a connectivity issue impacting data flow from the upstream system, resulting in unavailable Stock Allocations data. At this stage, the root cause has not yet been confirmed, and investigations are ongoing to determine where the issue originates.

3. identified Jul 17, 2026, 09:00 AM UTC

   We are currently experiencing an issue affecting the Stock Allocations data feed from LINX. The disruption is due to a connectivity issue impacting data flow from the upstream system, resulting in unavailable Stock Allocations data. At this stage, the root cause has not yet been confirmed, and investigations are ongoing to determine where the issue originates. The LINX technical team are aware of the issue and are currently investigating.

4. monitoring Jul 17, 2026, 09:17 AM UTC

   Connectivity to Network Rail's LINX Stock Allocations feed has been restored following a fix implemented by the LINX technical team. We are monitoring the data feed and assessing approaches to address any data gaps.

5. monitoring Jul 17, 2026, 10:02 AM UTC

   The feed of Stock Allocations from Network Rail's LINX has been restored and delayed messages are being processed. Services are returning to normal, with the backlog expected to clear within the next 15-30 minutes.

6. monitoring Jul 17, 2026, 10:36 AM UTC

   The feed of Stock Allocations from Network Rail's LINX has been restored and delayed messages have now been processed. We are continuing to monitor the feed.

7. resolved Jul 17, 2026, 11:36 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 13, 2026, 07:31 AM UTC· resolved Apr 13, 2026, 01:38 PM UTC

1. investigating Apr 13, 2026, 07:31 AM UTC

   We have have identified an issue with our Single Sign-On Services (Identity), some customers may be unable to reach the portal and applications. We apologise for any inconvenience and will post another update as soon as we learn more.

2. investigating Apr 13, 2026, 07:32 AM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 13, 2026, 11:12 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Apr 13, 2026, 01:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 10, 2026, 10:35 AM UTC· resolved Mar 10, 2026, 11:22 AM UTC

1. investigating Mar 10, 2026, 10:35 AM UTC

   We have identified issues receiving data. This may impact the data used in the replay functionality.

2. monitoring Mar 10, 2026, 11:01 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 10, 2026, 11:22 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 13, 2026, 12:21 PM UTC· resolved Feb 27, 2026, 09:34 AM UTC

1. investigating Feb 18, 2026, 09:33 AM UTC

   Berth Maps is receiving incorrect GPS data from some GWR services. Service location by TD and TRUST are not affected. We have raised it with the GPS data supplier.

2. resolved Feb 27, 2026, 09:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 13, 2025, 08:00 PM UTC· resolved Dec 14, 2025, 08:08 AM UTC

1. investigating Dec 13, 2025, 08:00 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Dec 13, 2025, 08:14 PM UTC

   There was a temporary drop in data from the TD.net feeds.

3. monitoring Dec 13, 2025, 10:29 PM UTC

   The fluctuations in the data feed are still being observed, and we are continuing to monitor them.

4. monitoring Dec 14, 2025, 02:13 AM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

5. resolved Dec 14, 2025, 08:08 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 06, 2025, 07:30 PM UTC· resolved Dec 07, 2025, 01:11 AM UTC

1. investigating Dec 06, 2025, 07:30 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Dec 06, 2025, 07:46 PM UTC

   There was a temporary drop in data from the TD.net feeds.

3. monitoring Dec 06, 2025, 09:43 PM UTC

   The fluctuations in the data feed are still being observed, and we are continuing to monitor them.

4. resolved Dec 07, 2025, 01:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 07:25 PM UTC· resolved Dec 06, 2025, 12:10 AM UTC

1. investigating Dec 05, 2025, 07:25 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Dec 05, 2025, 08:14 PM UTC

   There was a temporary drop in data from the TD.net feeds.

3. monitoring Dec 05, 2025, 10:11 PM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

4. resolved Dec 06, 2025, 12:10 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 30, 2025, 07:20 PM UTC· resolved Dec 01, 2025, 12:26 AM UTC

1. investigating Nov 30, 2025, 07:20 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Nov 30, 2025, 07:27 PM UTC

   There is a drop in the data from the TD.net feed, and we are monitoring the results.

3. monitoring Nov 30, 2025, 08:37 PM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

4. resolved Dec 01, 2025, 12:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 30, 2025, 01:30 AM UTC· resolved Nov 30, 2025, 04:51 AM UTC

1. investigating Nov 30, 2025, 01:30 AM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Nov 30, 2025, 01:54 AM UTC

   There is a drop in the data from the TD.net feed, and we are monitoring the results.

3. monitoring Nov 30, 2025, 02:18 AM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

4. resolved Nov 30, 2025, 04:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 29, 2025, 06:11 PM UTC· resolved Nov 30, 2025, 12:11 AM UTC

1. investigating Nov 29, 2025, 06:11 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. monitoring Nov 29, 2025, 06:53 PM UTC

   There was a temporary drop in data from the TD.net feeds, but these appear to have recovered.

3. monitoring Nov 29, 2025, 09:38 PM UTC

   The fluctuations in the data feed are still being observed, and we are continuing to monitor them.

4. resolved Nov 30, 2025, 12:11 AM UTC

   This incident has been resolved

Read the full incident report →

Started Nov 26, 2025, 06:06 PM UTC· resolved Nov 27, 2025, 12:13 AM UTC

1. investigating Nov 26, 2025, 06:06 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Nov 26, 2025, 06:35 PM UTC

   There was a temporary drop in data from the TD.net feeds, but these appear to have recovered.

3. monitoring Nov 26, 2025, 06:39 PM UTC

   The data feed has been recovered, and we are currently monitoring it.

4. identified Nov 26, 2025, 07:13 PM UTC

   There is a drop in the data from the TD.net feed, and we are monitoring the results.

5. identified Nov 26, 2025, 09:14 PM UTC

   Data feeds have recovered, but some data quality issues may still persist for a few hours due to the earlier data loss.

6. monitoring Nov 27, 2025, 12:12 AM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

7. resolved Nov 27, 2025, 12:13 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 22, 2025, 08:35 PM UTC· resolved Nov 23, 2025, 01:07 AM UTC

1. investigating Nov 22, 2025, 08:35 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Nov 22, 2025, 09:48 PM UTC

   There was a temporary drop in data from the TD.net feeds, but these appear to have recovered.

3. monitoring Nov 22, 2025, 09:50 PM UTC

   There was a drop in the data from the TD.net feed, and we are monitoring the results.

4. resolved Nov 23, 2025, 01:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 21, 2025, 09:40 AM UTC· resolved Nov 21, 2025, 11:02 AM UTC

1. investigating Nov 21, 2025, 09:40 AM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Nov 21, 2025, 09:59 AM UTC

   The issue has been identified, and there is a temporary drop in data from the TD.net feeds.

3. resolved Nov 21, 2025, 11:02 AM UTC

   This was a low impact data quality issue caused by yesterday’s blip in the trust feeds.

Read the full incident report →

Started Nov 20, 2025, 08:41 PM UTC· resolved Nov 21, 2025, 04:19 AM UTC

1. investigating Nov 20, 2025, 08:41 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Nov 20, 2025, 08:50 PM UTC

   The issue has been identified, and there is a temporary drop in data from the TD.net feeds.

3. identified Nov 20, 2025, 10:46 PM UTC

   There is a drop in the data from the TD.net feed, and we are monitoring the results.

4. identified Nov 21, 2025, 12:56 AM UTC

   Data feeds have recovered, but some data quality issues may still persist for a few hours due to the earlier data loss.

5. monitoring Nov 21, 2025, 02:00 AM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

6. resolved Nov 21, 2025, 04:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 19, 2025, 09:46 AM UTC· resolved Nov 20, 2025, 09:27 AM UTC

1. investigating Nov 19, 2025, 09:46 AM UTC

   Sirocco and Berth Maps are not receiving stock allocations. We are investigating the cause.

2. resolved Nov 20, 2025, 09:27 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2025, 09:30 PM UTC· resolved Nov 05, 2025, 03:43 AM UTC

1. investigating Nov 04, 2025, 09:30 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Nov 04, 2025, 09:38 PM UTC

   There was a temporary drop in data from the TD.net feeds, but these appear to have recovered.

3. identified Nov 04, 2025, 11:25 PM UTC

   There is a drop in the data from the TD.net feed, and we are monitoring the results.

4. monitoring Nov 05, 2025, 12:13 AM UTC

   The data feeds appear to have recovered now, and we are monitoring the results.

5. resolved Nov 05, 2025, 03:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2025, 05:25 PM UTC· resolved Oct 24, 2025, 12:22 AM UTC

1. investigating Oct 23, 2025, 05:25 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Oct 23, 2025, 05:45 PM UTC

   The issue has been identified, and there is a temporary drop in data from the TD.net feeds.

3. identified Oct 23, 2025, 07:38 PM UTC

   The fluctuations in the data feed are still being observed, and we are continuing to monitor them.

4. monitoring Oct 23, 2025, 09:44 PM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

5. resolved Oct 24, 2025, 12:22 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2025, 04:00 AM UTC· resolved Oct 23, 2025, 02:15 PM UTC

1. investigating Oct 23, 2025, 04:00 AM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Oct 23, 2025, 04:28 AM UTC

   There was a temporary drop in data from the TD.net feeds, but these appear to have recovered.

3. identified Oct 23, 2025, 08:19 AM UTC

   There is a drop in the data from the TD.net feed, and we are monitoring the results.

4. monitoring Oct 23, 2025, 10:39 AM UTC

   The data feeds appear to have recovered now, and we are monitoring the results.

5. resolved Oct 23, 2025, 02:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 02:51 PM UTC· resolved Oct 21, 2025, 11:43 AM UTC

1. investigating Oct 20, 2025, 02:51 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Oct 20, 2025, 03:05 PM UTC

   There was a temporary drop in data from the TD.net feeds, but these appear to have recovered.

3. identified Oct 20, 2025, 04:04 PM UTC

   There is a drop in the data from the TD.net feed, and we are monitoring the results.

4. identified Oct 20, 2025, 06:11 PM UTC

   Data feeds have recovered, but some data quality issues may persist for a few hours due to the earlier data loss.

5. identified Oct 20, 2025, 08:38 PM UTC

   Data feeds have recovered, but some data quality issues may persist for a few hours due to the earlier data loss.

6. identified Oct 21, 2025, 01:07 AM UTC

   Data feeds have recovered, but some data quality issues may still persist for a few hours due to the earlier data loss.

7. identified Oct 21, 2025, 03:46 AM UTC

   Data feeds have recovered, but some data quality issues may still persist for a few hours due to the earlier data loss.

8. monitoring Oct 21, 2025, 10:45 AM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

9. resolved Oct 21, 2025, 11:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 16, 2025, 02:50 AM UTC· resolved Oct 16, 2025, 06:15 AM UTC

1. investigating Oct 16, 2025, 02:50 AM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Oct 16, 2025, 03:03 AM UTC

   There was a temporary drop in data from the TD.net feeds, but these appear to have recovered

3. monitoring Oct 16, 2025, 06:03 AM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

4. resolved Oct 16, 2025, 06:15 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 15, 2025, 05:31 PM UTC· resolved Oct 16, 2025, 01:36 AM UTC

1. investigating Oct 15, 2025, 05:31 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Oct 15, 2025, 05:42 PM UTC

   There was a temporary drop in data from the TD.net feeds, but these appear to have recovered.

3. monitoring Oct 15, 2025, 06:18 PM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

4. monitoring Oct 15, 2025, 06:36 PM UTC

   Data feeds have recovered, but some data quality issues may persist for a few hours due to the earlier data loss.

5. monitoring Oct 16, 2025, 12:14 AM UTC

   Data feeds have recovered, but some data quality issues may persist for a few hours due to the earlier data loss.

6. resolved Oct 16, 2025, 01:36 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 08, 2025, 03:25 PM UTC· resolved Oct 08, 2025, 08:02 PM UTC

1. investigating Oct 08, 2025, 03:25 PM UTC

   An exception has been detected with the TD.net datafeeds. This has been raised with the support team, and is under investigation.

2. identified Oct 08, 2025, 03:37 PM UTC

   The issue has been identified, and there is a temporary drop in data from the TD.net feeds.

3. monitoring Oct 08, 2025, 05:41 PM UTC

   TD.net feeds have been recovered, and we are continuing to monitor for any further issues.

4. resolved Oct 08, 2025, 08:02 PM UTC

   This incident has been resolved.

Read the full incident report →