LexisNexis Cirium incident
Partial Outage with Advance Booking report
LexisNexis Cirium experienced a minor incident on January 15, 2026 affecting Advanced Bookings, lasting 12d 10h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 14, 2026, 10:40 PM UTC
We’re currently experiencing degraded performance issues with the Advance Booking report. Advance Booking Compare functionality is currently unavailable. The rest of the Advance Booking functionality has not been impacted. Our team is currently working to restore normal performance levels. We apologize for any inconvenience. Advance Booking users may be affected.
- investigating Jan 15, 2026, 06:55 AM UTC
We are continuing to investigate the issue and will provide another update by 14:48 UTC on 2026-01-15. Our apologies again for the inconvenience. Please contact our Help Desk with any questions.
- investigating Jan 15, 2026, 06:56 AM UTC
We are continuing to investigate this issue.
- investigating Jan 15, 2026, 02:56 PM UTC
We are continuing to investigate the issue and will provide another update by 22:55 UTC on 2026-01-15. Our apologies for the continued disruption. Pease contact our Help Desk with any questions.
- investigating Jan 15, 2026, 10:59 PM UTC
We are continuing to investigate the issue and will provide the next update by 06:55 UTC on 2026-01-16. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk.
- investigating Jan 16, 2026, 06:58 AM UTC
We are continuing to investigate the issue and will provide the next update by 14:55 UTC on 2026-01-16. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk.
- identified Jan 16, 2026, 03:36 PM UTC
We have identified the issue and are actively working on a resolution. The next update will be provided by 22:55 UTC on 2026-01-16. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.
- identified Jan 17, 2026, 07:12 AM UTC
We have identified the issue and are actively working on a resolution. The next update will be provided by 14:55 UTC on 2026-01-17. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.
- identified Jan 17, 2026, 02:57 PM UTC
We have identified the issue and are actively working on a resolution. The next update will be provided by 22:55 UTC on 2026-01-17. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.
- identified Jan 17, 2026, 10:56 PM UTC
We have identified the issue and are actively working on a resolution. The next update will be provided by 06:55 UTC on 2026-01-18. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.
- identified Jan 18, 2026, 06:55 AM UTC
We have identified the issue and are actively working on a resolution. The next update will be provided by 14:55 UTC on 2026-01-18. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.
- identified Jan 18, 2026, 02:56 PM UTC
We have identified the issue and are actively working on a resolution. The next update will be provided by 22:55 UTC on 2026-01-18. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.
- identified Jan 18, 2026, 11:12 PM UTC
We have identified the issue and are actively working toward a resolution. Our next update will be provided by 06:55 UTC on 19 January 2026. We apologize for the continued disruption. If you have any questions, please contact our Help Desk. Thank you for your patience—we will share further updates as soon as they become available.
- identified Jan 19, 2026, 07:23 AM UTC
We have identified the issue and are actively working on a resolution. The next update will be provided by 14:55 UTC on 2026-01-19. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.
- identified Jan 19, 2026, 01:06 PM UTC
Our engineers are working on a fix for the missing Compare functionality, with live release expected by the end of this week. Please check back for further updates.
- identified Jan 20, 2026, 07:01 AM UTC
We have identified the issue causing the missing Compare functionality and are actively working on a resolution. Our engineers are implementing a fix, with a live release expected by the end of this week. We apologize for the ongoing disruption and appreciate your patience. If you have any questions, please contact our Help Desk.
- identified Jan 20, 2026, 04:35 PM UTC
We are continuing to work on a fix for this issue.
- identified Jan 24, 2026, 02:31 AM UTC
We are continuing to test a fix, with production deployment targeted for Tuesday, 27th January. We will provide another update once a fix is deployed. Thank you for your continued patience.
- resolved Jan 27, 2026, 04:57 PM UTC
This incident has been resolved. Users can now run comparisons for multiple airports, cities, countries, and continents.