LexisNexis Cirium Outage History

Started Aug 10, 2026, 09:04 PM UTC· resolved Aug 12, 2026, 11:31 AM UTC

1. investigating Aug 10, 2026, 09:04 PM UTC

   We are investigating an issue where some requests to the Flight Track API and Historical Flight Status API endpoints are returning intermittent timeout errors. Our engineering team is actively working to identify and resolve the root cause. Updates will be provided as soon as more information becomes available.

2. investigating Aug 11, 2026, 05:04 AM UTC

   We continue to investigate the issue affecting the Flight Track API and Historical Flight Status API. Our team is actively working on a resolution and will provide updates as they become available. If you have any questions or are experiencing this issue, please contact [email protected]

3. investigating Aug 11, 2026, 01:10 PM UTC

   Our engineers have restarted the affected database, and although an improvement in performance has been observed, some timeout errors are still occurring. Investigation of the underlying cause is continuing and a further update will be posted no later than 21:10 UTC. Thank you for your understanding. Please contact the Helpdesk if you require support.

4. monitoring Aug 11, 2026, 05:15 PM UTC

   The database instance upgrade has been completed, and service stability has improved. The Current Flight Tracks API is now operating normally, and the Historical Flight Status API also appears stable at this time. We will continue to closely monitor both services and investigate the underlying root cause. We will provide a further update by 05:30 AM UTC on 2026-08-12 with any additional findings. We appreciate your patience.

5. monitoring Aug 12, 2026, 05:33 AM UTC

   Following recent service improvements, the affected service is now operating normally. We are continuing to optimize performance across our platform to enhance stability and reliability. We remain closely monitoring all services and will provide further updates. Thank you for your patience and understanding.

6. resolved Aug 12, 2026, 11:31 AM UTC

   This incident has been resolved. All affected APIs are operating normally. Please contact the Helpdesk should you observe any ongoing performance issues.

Read the full incident report →

Started Aug 10, 2026, 08:28 PM UTC· resolved Aug 11, 2026, 11:32 AM UTC

1. investigating Aug 10, 2026, 08:28 PM UTC

   We are currently investigating an issue affecting FlightStats.com. Users may experience slow performance, intermittent unavailability, and difficulties retrieving historical flight information. Our team is actively working to restore normal service and will provide updates as more information becomes available. Our apologies for the inconvenience.

2. investigating Aug 11, 2026, 04:30 AM UTC

   We continue to investigate the issue affecting Flightstats.com. Our team is actively working on a resolution and will provide updates as more information becomes available. If you have any questions or are experiencing this issue, please contact [email protected]

3. resolved Aug 11, 2026, 11:32 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 04, 2026, 06:08 AM UTC· resolved Aug 04, 2026, 07:25 AM UTC

1. investigating Aug 04, 2026, 06:08 AM UTC

   We’re currently experiencing degraded performance issues with Sky API. Our team is currently working to restore normal performance levels. We apologize for any inconvenience. Sky API users may be affected. Next update in 08:15 am UTC.

2. resolved Aug 04, 2026, 07:25 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 02, 2026, 03:02 PM UTC· resolved Aug 03, 2026, 06:37 AM UTC

1. investigating Aug 02, 2026, 03:02 PM UTC

   We are investigating reports of Aircraft Summary pages displaying incomplete or invalid aircraft information in Fleets Analyzer. Some users may experience missing data fields or aircraft details failing to load as expected. Our team is actively reviewing the issue. If you have any questions or are experiencing this issue, please contact [email protected].

2. investigating Aug 02, 2026, 07:02 PM UTC

   We continue to investigate the issue affecting Aircraft Summary pages in Fleets Analyzer. Some users may still experience missing or incomplete aircraft information. Our team is actively working on a resolution. If you have any questions or are experiencing this issue, please contact [email protected].

3. investigating Aug 03, 2026, 03:20 AM UTC

   We are still continuing investigation of the issue in Fleets Analyzer. Our team is actively working on a resolution. If you have any questions or are experiencing this issue, please contact [email protected].

4. monitoring Aug 03, 2026, 05:20 AM UTC

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

5. resolved Aug 03, 2026, 06:37 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 17, 2026, 10:07 AM UTC· resolved Jul 20, 2026, 01:30 PM UTC

1. investigating Jul 17, 2026, 10:07 AM UTC

   We are currently investigating an upstream issue affecting Schedule data ingestion into the Sky Warehouse, which started on July 17, 2026 at 09:00 UTC and is resulting in stale data. At present, schedule data from July 16 onward is unavailable, with the most recent available data dated July 15. Our team is actively working to resolve the issue and restore normal data flow. Further updates will be provided as more information becomes available. Please contact our Help Desk if you have any questions.

2. resolved Jul 17, 2026, 05:46 PM UTC

   The upstream issue affecting Schedule data ingestion into Sky Warehouse has been resolved, and normal data flow has been restored. Schedule data is now current and available as expected. We apologize for any inconvenience and appreciate your patience while our team worked to address the issue.

Read the full incident report →

Started Jul 13, 2026, 01:53 PM UTC· resolved Jul 13, 2026, 03:49 PM UTC

1. resolved Jul 13, 2026, 04:29 PM UTC

   On Monday, 13th July 2026 from 13:53 UTC to 15:49 UTC, customers experienced HTTP 503 errors when accessing the Historical Flight Status API and no data returned from the Historical Flight Status tool on FlightStats.com. We have addressed the issue and increased the database storage allocation, restoring normal service operation. This incident has been resolved and the service remains stable while we continue to monitor.

Read the full incident report →

Started Jul 08, 2026, 08:48 AM UTC· resolved Jul 17, 2026, 08:12 AM UTC

1. identified Jul 08, 2026, 08:48 AM UTC

   Values Analyzer - Online Values are temporarily unavailable due to an issue with the engine maintenance cost data. The following assets are affected: Boeing 777-200LR, 200LRF, 200LRMF, 300ER, 300ERSF/MF/CF Boeing 767-300ER, 300ERF, 300SF/BCF, 200ER CRJ700, CRJ900, CRJ1000 General Electric GE90-110, GE90-115 General Electric CF6-80C2B6F General Electric CF34-8C5B1, 8C5A2, 8C5A3 Our engineers are working on the data fix. In the meantime, users will be prompted to request a Desktop Valuation. Please contact our Helpdesk with any questions.

2. resolved Jul 17, 2026, 08:12 AM UTC

   This incident has been resolved and Online Valuations can be ran for all the affected assets. Please accept our apologies for any disruption caused.

Read the full incident report →

Started Jul 02, 2026, 02:17 PM UTC· resolved Jul 02, 2026, 03:34 PM UTC

1. investigating Jul 02, 2026, 02:17 PM UTC

   We’re experiencing a service outage with Diio Mi and SRS Analyser. Users are observing a 500 Error response when trying to run any schedule, FM Traffic or US DOT reports. Our team is currently working to restore the service. We apologize for any inconvenience. We will provide a further updated no later than 18:15 UTC.

2. investigating Jul 02, 2026, 03:00 PM UTC

   Full access to SRS Analyser has been restored. We are still seeing some issues in Diio Mi and are continuing to investigate.

3. resolved Jul 02, 2026, 03:34 PM UTC

   The incident has been resolved across all affected services. Please accept our apologies for any disruption caused and contact the Helpdesk should you require further assistance.

Read the full incident report →

Started Jun 22, 2026, 10:13 AM UTC· resolved Jun 22, 2026, 04:37 PM UTC

1. investigating Jun 22, 2026, 10:13 AM UTC

   Cirium’s SFTP service is experiencing a degradation in service. Any customer attempting to connect and download their files using this service (eft.lexisnexisrisk.com) will currently be unable to do so. We are actively working on restoring the service and will provide regular updates and also advise when this incident is resolved. Please accept our apologies for the inconvenience caused.

2. monitoring Jun 22, 2026, 12:21 PM UTC

   Cirium’s SFTP service has now been restored, and we are in the process of uploading files to the relevant customer sub-folders located in this service: (eft.lexisnexisrisk.com). Once all deliveries have been completed we will provide a final update and resolution here. Once again, we apologise for the inconvenience caused.

3. resolved Jun 22, 2026, 04:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 09, 2026, 12:21 PM UTC· resolved Jun 09, 2026, 01:49 PM UTC

1. investigating Jun 09, 2026, 12:21 PM UTC

   We are experiencing a service outage affecting Diio Mi and SRS Analyser. Users are observing a 500 Error. Our engineers are investigating and we will post an update no later than 1600 UTC. Please accept our apologies for any inconvenience caused by the outage and contact our Helpdesk with any questions.

2. resolved Jun 09, 2026, 01:49 PM UTC

   Our engineers have identified the root cause of the issue. A fix has been applied and full access has been restored. The issue is now resolved.

Read the full incident report →

Started May 09, 2026, 12:45 PM UTC· resolved May 09, 2026, 05:29 PM UTC

1. investigating May 09, 2026, 12:45 PM UTC

   We are currently investigating reports of HTTP 503 (Service Unavailable) responses affecting the FlightStats Flex Historical Flight Status API. At this time, the issue appears to be impacting a subset of requests to the historical flight status endpoint. Our engineering teams have been notified and are actively working to identify the cause and restore normal service as quickly as possible. We will provide an update on or before May 9, 2026 at 15:30 UTC, as more information becomes available. Thank you for your patience.

2. identified May 09, 2026, 02:35 PM UTC

   Our engineers have identified the issue impacting the FlightStats Flex Historical Flight Status API and are actively working toward a resolution. We will continue to share updates here as progress is made. Thank you for your patience, and we apologize for the inconvenience.

3. resolved May 09, 2026, 05:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 08:26 AM UTC· resolved May 08, 2026, 04:18 PM UTC

1. investigating May 08, 2026, 08:26 AM UTC

   We are currently investigating reports of degraded performance affecting the Sky Stream NOTAMs feed, which appears to be related to an AWS service disruption in the US‑East‑1 region. As a result, some customers may notice a reduction in message frequency on the NOTAMs feed. As a precaution, we are also reviewing other Cirium services to assess whether they may be impacted by the same AWS disruption. Our teams are actively monitoring the situation and continuing to investigate. Further updates will be shared as more information becomes available. Thank you for your patience and understanding.

2. investigating May 08, 2026, 03:08 PM UTC

   The AWS outage causing an unscheduled data source outage is still active with AWS continuing to work on the issue. https://health.aws.amazon.com/health/status

3. resolved May 08, 2026, 04:18 PM UTC

   Our NOTAM feed has been fully restored and no other downstream issues have been observed.

Read the full incident report →

Started May 03, 2026, 08:30 AM UTC· resolved May 03, 2026, 12:32 PM UTC

1. investigating May 03, 2026, 08:30 AM UTC

   We would like to inform you that we are currently experiencing a service issue affecting access to FlightStats.com, which began at approximately 7:02 UTC on 3 May. During this time, customers may encounter difficulties with logging in and resetting passwords. Our Engineering team is actively investigating the issue and working to determine the root cause. This matter is being treated as a high‑priority incident. We sincerely apologize for the inconvenience this may cause and greatly appreciate your patience as we work to restore full service. We will share the next update on or before 03 May 2026 at 12:26 UTC. If you require immediate assistance, please contact our Customer Support team, who will be happy to help.

2. identified May 03, 2026, 11:00 AM UTC

   The issue has been identified, and a fix is currently being implemented. Our Engineering team is actively working on it, and we will continue to provide updates as they become available. Thank you for your understanding.

3. identified May 03, 2026, 11:10 AM UTC

   Our Engineering team has identified the issue and is actively working on a resolution. Efforts to restore normal login access are ongoing, and we continue to closely monitor the situation. We will provide the next update within the next hour. Thank you for your patience and understanding.

4. identified May 03, 2026, 12:24 PM UTC

   This issue, which impacted user login and access to FlightStats.com, has been resolved, and normal service has been fully restored. All necessary corrective actions have been completed, and the platform is stable following post‑resolution monitoring. We sincerely apologize for the inconvenience this may have caused and would like to thank you for your patience and understanding throughout the incident.

5. identified May 03, 2026, 12:30 PM UTC

   We are continuing to work on a fix for this issue.

6. resolved May 03, 2026, 12:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 01, 2026, 11:50 AM UTC· resolved May 01, 2026, 12:15 PM UTC

1. resolved May 01, 2026, 12:45 PM UTC

   We experienced a short access and entitlement service outage today, 1st May, from approximately 11:50 to 12:15 UTC. The outage affected multiple products, including but not limited to Fleets Analyzer, Values Analyzer, and Dashboard. The service has been restored and all products are fully operational. We apologize for any inconvenience caused by the outage. Please contact our help desk with any questions

Read the full incident report →

Started Apr 25, 2026, 05:31 PM UTC· resolved Apr 27, 2026, 11:08 AM UTC

1. investigating Apr 25, 2026, 05:31 PM UTC

   We are currently experiencing degraded performance affecting Cirium Sky™ Stream, specifically the Flight Status Stream, where users may encounter UPSTREAM_ERROR (500) responses when attempting to connect. The issue has been reported to our Engineering team and is currently under investigation. We apologize for any inconvenience this may cause. An update will be provided on or before 02:07 UTC on 26 April 2026.

2. investigating Apr 26, 2026, 01:38 AM UTC

   We are continuing the investigation of this issue. We will provide you an update we identify the cause of this issue. Thank you for your continued patience and understanding.

3. investigating Apr 26, 2026, 10:33 AM UTC

   We are continuing to investigate this issue, and our Engineering team is actively working to identify the root cause. We will provide an update as soon as more information becomes available. The next scheduled update will be shared on or before 18:35 UTC on 26 April 2026. Thank you for your continued patience and understanding.

4. investigating Apr 26, 2026, 05:53 PM UTC

   We are continuing to investigate this issue, and our Engineering team is actively working to identify the root cause. We will provide an update as soon as more information becomes available. The next scheduled update will be shared on or before 2:35 UTC on 27 April 2026. Thank you for your continued patience and understanding.

5. investigating Apr 27, 2026, 04:54 AM UTC

   We are continuing to investigate this issue, and our Engineering team is actively working to identify the root cause. We will provide an update as soon as more information becomes available. The next scheduled update will be shared on or before 10:35 UTC on 27 April 2026. Thank you for your continued patience and understanding.

Read the full incident report →

Started Apr 24, 2026, 02:19 PM UTC· resolved Apr 25, 2026, 03:44 AM UTC

1. identified Apr 24, 2026, 02:19 PM UTC

   We’re currently experiencing a data ingestion issue affecting Cirium Sky™ Warehouse customers using Redshift. From 23 April 2026 at 08:00 GMT, new data stopped being published to all Redshift tables, resulting in stale data across affected services. Customers relying on this data for airline and airport operations, analytics, and logistics may be impacted. Our engineers have started manual backfilling, and data is gradually becoming available again. The team is working on backfilling each table, hence the data will be available gradually, investigating the underlying root cause, and closely monitoring new runs to ensure data updates resume as expected. We sincerely apologize for any inconvenience caused. Updates will be provided every 8 hours. The next update will be shared on or before 22:19 UTC.

2. identified Apr 24, 2026, 06:59 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Apr 24, 2026, 07:00 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Apr 24, 2026, 07:01 PM UTC

   We are currently investigating an ongoing issue impacting the availability of data for a subset of scheduled processing during the period between 23 April 08:00 and 24 April, approximately 16:30 (UTC). Restoration activities are underway, and reprocessing has been completed for workloads affected during this timeframe. Data generated after approximately 16:30 (UTC) is still in the process of being restored and may not yet be visible. A fix has been applied, and we are actively validating the solution. Additional reprocessing is planned today, and we will provide an update on expected run timing by 22:00 UK time. We will continue to share updates as progress is made. Thank you for your patience while we work to fully resolve this issue.

5. identified Apr 24, 2026, 07:01 PM UTC

   We are continuing to work on a fix for this issue.

6. identified Apr 24, 2026, 11:47 PM UTC

   Our engineers had completed the backfill till 24 Apr 22:00. Thank you for your patience while we work to fully resolve this issue.

7. identified Apr 25, 2026, 01:06 AM UTC

   Our Engineers have applied the fix to production and we have verified that it is working. Additionally, our Engineers have also backfilled the tables till now. The data in Redshift is now up to date. We will continue to monitor the situation and provide an update once we identify that the situation is fully resolved. Thank you for your continued patience.

8. monitoring Apr 25, 2026, 01:07 AM UTC

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

9. resolved Apr 25, 2026, 03:44 AM UTC

   This incident is now resolved and we will continue to monitor if any issue arises. Thank you for your patience. Please let us know if you have any questions.

Read the full incident report →

Started Apr 17, 2026, 08:35 AM UTC· resolved Apr 17, 2026, 11:32 AM UTC

1. investigating Apr 17, 2026, 08:35 AM UTC

   We’re currently experiencing degraded performance issues affecting all products where fleets data is surfaced, including, but not limited to Fleets Analyzer and Cirium Sky™ Warehouse. The overnight data publication failed, resulting in stale data in all affected services. The issue has also meant that no news articles have been published in Dashboard or Pulse since midnight (UTC). Our engineers are working to restore the affected services and address the underlying cause. We sincerely apologize for any inconvenience caused. The next update will be posted on or before 16:30 UTC.

2. resolved Apr 17, 2026, 11:32 AM UTC

   Our engineers have successfully completed the fleets data update. The latest data will be applied to all affected products as per their individual update schedules. An internal RCA is scheduled to fully understand the cause(s) of the recent incidents affecting the Ascend product family, and agree steps to enhance platform resilience.

Read the full incident report →

Started Apr 17, 2026, 01:51 AM UTC· resolved Apr 17, 2026, 05:30 AM UTC

1. investigating Apr 17, 2026, 01:51 AM UTC

   We’re currently experiencing an issue with Dashboard and Values Analyzer. In both services, the page is not functioning as expected. In Values Analyzer, users are unable to run valuation. In Dashboard, no news content is published. Our engineers are working to restore normal performance levels. We apologize for any inconvenience caused. The next update will be posted on or before 05:44 UTC.

2. resolved Apr 17, 2026, 05:30 AM UTC

   Our engineers have identified the root cause of the issue. A fix has been applied to restore normal performance levels. The issue is now resolved.

Read the full incident report →

Started Apr 16, 2026, 11:17 PM UTC· resolved Apr 17, 2026, 09:46 AM UTC

1. investigating Apr 16, 2026, 11:17 PM UTC

   We are currently experiencing an issue impacting the delivery of Trip alerts. The issue started at approx. 19:18 UTC today on 16 April 2026 and has been escalated to our engineering team. We will provide a further update by 02:48 UTC on 17 April 2026.

2. investigating Apr 17, 2026, 02:48 AM UTC

   Our engineering team continues to investigate the issue impacting Trip alert delivery We will provide another update by 06:48 UTC on 17th April 2026.

3. identified Apr 17, 2026, 05:40 AM UTC

   Our engineering team has identified the root cause, and they are currently addressing the issue. We will provide another update by 09:40UTC on 17th April 2026.

4. resolved Apr 17, 2026, 09:46 AM UTC

   The incident affecting Trip alert deliveries has been resolved. Alerts are being delivered successfully and we are continuing to monitor performance closely. Please accept our apologies for any her disruption caused and contact the Help Desk if you have any questions.

Read the full incident report →

Started Apr 14, 2026, 09:53 PM UTC· resolved Apr 15, 2026, 03:49 AM UTC

1. investigating Apr 14, 2026, 09:53 PM UTC

   We are investigating reports of missing alerts from the Alerts API service from approximately 18:18 UTC today on 2026-04-14. We will provide another update by 1:47 AM UTC on 2026-04-15.

2. identified Apr 15, 2026, 02:32 AM UTC

   We have identified the root cause of the issue and are actively working on a resolution. We will provide another update by 05:47 UTC on 2026-04-15.

3. monitoring Apr 15, 2026, 02:41 AM UTC

   Our team has identified the cause, and alert delivery has been successfully resumed. We are currently monitoring to ensure ongoing stability.

4. resolved Apr 15, 2026, 03:49 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 14, 2026, 09:29 AM UTC· resolved Apr 14, 2026, 11:02 AM UTC

1. investigating Apr 14, 2026, 09:29 AM UTC

   We are investigating an issue affecting the Schedule Snapshot platform. The service returning a server error response. We apologize for any inconvenience caused. The next update will be posted on or before 13:30 UTC.

2. resolved Apr 14, 2026, 11:02 AM UTC

   The incident has been resolved and the service is performing as expected.

Read the full incident report →

Started Apr 14, 2026, 08:27 AM UTC· resolved Apr 14, 2026, 11:41 AM UTC

1. investigating Apr 14, 2026, 08:27 AM UTC

   We’re currently experiencing degraded performance issues affecting all products where fleets data is surfaced, including, but not limited to Fleets Analyzer and Cirium Sky™ Warehouse. It appears that data was not published overnight on Monday, 13th April, resulting in stale data in all affected services. The issue has also meant that no news articles have been published in Dashboard or Pulse since midnight (UTC). Our engineers are working to restore the affected services and address the underlying cause. We sincerely apologize for any inconvenience caused. The next update will be posted on or before 12:25 UTC.

2. resolved Apr 14, 2026, 11:41 AM UTC

   Our engineers have successfully completed the fleets data update. The latest data will be applied to all affected products as per their individual update schedules. An internal RCA will be carried out to understand the cause(s) of today's and yesterday's incidents, and steps put in place to enhance platform resilience.

Read the full incident report →

Started Apr 13, 2026, 10:26 AM UTC· resolved Apr 13, 2026, 11:56 AM UTC

1. investigating Apr 13, 2026, 10:26 AM UTC

   We’re currently experiencing degraded performance issues with Fleets Analyzer and the Fleets tables in Cirium Sky™ Warehouse. No data was published on Sunday, 12th April, resulting in stale data in both services. Our engineers are investigating. We apologize for any inconvenience caused. The next update will be posted on or before 14:25 UTC.

2. resolved Apr 13, 2026, 11:56 AM UTC

   This incident has been resolved. We have successfully refreshed the fleets data and this update will flow through to Fleets Analyzer and Cirium Sky™ Warehouse.

Read the full incident report →

Started Apr 13, 2026, 10:20 AM UTC· resolved Apr 13, 2026, 11:57 AM UTC

1. investigating Apr 13, 2026, 10:20 AM UTC

   We’re currently experiencing degraded performance issues with Fleets and Values Analyzer. In both services, auto-suggest is not working. In Fleets Analyzer, users can work around the issue by using the Filter menu. In Values Analyzer, there is no workaround to create a new generic or specific valuation. Our engineers are working to restore normal performance levels. We apologize for any inconvenience caused. The next update will be posted on or before 14:20 UTC.

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

   Auto-suggest is now working. We will continue to monitor for a period before considering this incident resolved.

3. resolved Apr 13, 2026, 11:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 13, 2026, 08:31 AM UTC· resolved Apr 13, 2026, 11:57 AM UTC

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

   We are investigating an issue that is preventing the publication of new articles on the Dashboard and Pulse platforms. We apologise for any inconvenience and will provide an update no later than 16:30 UTC.

2. monitoring Apr 13, 2026, 10:41 AM UTC

   New articles are now appearing. We are continuing to investigate the cause and are monitoring performance closely.

3. resolved Apr 13, 2026, 11:57 AM UTC

   This incident has been resolved.

Read the full incident report →