LexisNexis Cirium incident

Reduced Message Frequency for Sky Stream Positional and Flight Status Feeds

Resolved after 12 days 2 hours, affecting Cirium Sky™ Stream, on September 30, 2026.

resolved Oct 12, 2026, 03:37 PM UTC

This incident has been resolved. The cutover to our data provider's new production environment has been completed successfully, with no issues detected. Users can expect to see increased message volumes as a result of the change. We are continuing to monitor data quality, volume, latency and service stability as part of our normal operational oversight.

Started
Sep 30, 2026, 01:17 PM UTC
Resolved
Oct 12, 2026, 03:37 PM UTC
Duration
12d 2h
Detected by Pingoru
Sep 30, 2026, 01:17 PM UTC

Affected components

Cirium Sky™ Stream

Update timeline

  1. investigating Sep 30, 2026, 01:17 PM UTC

    We are experiencing a further reoccurrence of the data degradation issue resulting in a reduced frequency of messages on the Sky Stream Positional and Flight Status Feeds. Our team is continuing to work with the data provider to find a permanent resolution. Please accept our apologies for the continued disruption and contact the Helpdesk with any questions.

  2. monitoring Sep 30, 2026, 05:06 PM UTC

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

  3. monitoring Sep 30, 2026, 08:20 PM UTC

    We are now receiving data from our upstream provider within expected volume and latency ranges. While the current service has returned to expected levels and appears stable, we will continue monitoring to ensure performance remains consistent. We will provide our next update at approximately 12:00 UTC on Thursday, 1 October.

  4. monitoring Oct 01, 2026, 01:17 PM UTC

    Data continues to be received within the expected volume and latency ranges. We will continue monitoring to ensure performance remains consistent and provide a further update at approximately 12:00 UTC on Thursday, 2nd October.

  5. monitoring Oct 02, 2026, 12:25 PM UTC

    Data continues to be received within the expected volume and latency ranges. We will monitor across the weekend to ensure the performance remains consistent. A further update will be provided at approximately 12:00 UTC on Monday 5th October.

  6. monitoring Oct 05, 2026, 12:51 PM UTC

    Data continues to be received within the expected volume and latency ranges. We are continuing to monitor whilst our data provider works on a new production environment. A further update will be provided at approximately 12:00 UTC on Wednesday 7th October.

  7. monitoring Oct 07, 2026, 12:36 PM UTC

    Data continues to be received within the expected volume and latency ranges. The cutover to the data provider's new production environment is scheduled for 17:00 UTC on Thursday, 8th October. A further update will be provided after the cutover, at approximately 18:00 UTC on 8th October.

  8. monitoring Oct 09, 2026, 12:36 AM UTC

    The final cut over to our upstream provider's new production environment is scheduled for 12:30 UTC on Friday 9th October assuming continued stability. A further update will be provided following the planned production switchover. Thank you for your patience.

  9. monitoring Oct 09, 2026, 12:05 PM UTC

    The final cutover to our upstream provider's new production environment has been rescheduled for Monday 12th October.. A further update will be provided following successful completion of the production switchover. Thank you for your patience.

  10. resolved Oct 12, 2026, 03:37 PM UTC

    This incident has been resolved. The cutover to our data provider's new production environment has been completed successfully, with no issues detected. Users can expect to see increased message volumes as a result of the change. We are continuing to monitor data quality, volume, latency and service stability as part of our normal operational oversight.

Your product runs on more than LexisNexis Cirium

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →