Is LexisNexis Cirium down?

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.

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.

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.

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.

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.

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.

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

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

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.

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

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

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.

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

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.