LexisNexis Cirium incident

Degraded Performance – Cirium Sky™ Stream (Flight Status Stream)

Minor Resolved View vendor source →

LexisNexis Cirium experienced a minor incident on April 25, 2026 affecting Cirium Sky™ Stream, lasting 1d 17h. The incident has been resolved; the full update timeline is below.

Started
Apr 25, 2026, 05:31 PM UTC
Resolved
Apr 27, 2026, 11:08 AM UTC
Duration
1d 17h
Detected by Pingoru
Apr 25, 2026, 05:31 PM UTC

Affected components

Cirium Sky™ Stream

Update timeline

  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.