LexisNexis Cirium incident
Sky Warehouse Redshift Data Delay – 23 April 2026 - 24 April 2026
Affected components
Update timeline
- 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.
- identified Apr 24, 2026, 06:59 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 24, 2026, 07:00 PM UTC
We are continuing to work on a fix for this issue.
- 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.
- identified Apr 24, 2026, 07:01 PM UTC
We are continuing to work on a fix for this issue.
- 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.
- 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.
- monitoring Apr 25, 2026, 01:07 AM UTC
A fix has been implemented and we are monitoring the results.
- 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.
Looking to track LexisNexis Cirium downtime and outages?
Pingoru polls LexisNexis Cirium's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when LexisNexis Cirium reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track LexisNexis Cirium alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required