LexisNexis Cirium incident

Missing data in Connections API for departure dates on or after 1/31/2026

Minor Resolved View vendor source →

LexisNexis Cirium experienced a minor incident on January 30, 2026 affecting Cirium Sky™ APIs, lasting 1d 2h. The incident has been resolved; the full update timeline is below.

Started
Jan 30, 2026, 11:28 PM UTC
Resolved
Feb 01, 2026, 01:35 AM UTC
Duration
1d 2h
Detected by Pingoru
Jan 30, 2026, 11:28 PM UTC

Affected components

Cirium Sky™ APIs

Update timeline

  1. investigating Jan 30, 2026, 11:28 PM UTC

    We are investigating an issue where the Connections API is returning no results for queries with departure dates on or after January 31, 2026. Queries for a departure date of today (January 30, 2026) are returning expected results. We will provide another update by 03:00 UTC on 2026-01-31.

  2. investigating Jan 31, 2026, 02:34 AM UTC

    We have identified the issue and it is only affecting cargo type searches. We are investigating the cargo data pipeline and will provide updates as more information becomes available. We will provide another update by 03:00 UTC on February 1, 2026. Thank you for your patience and apologies for any inconvenience.

  3. resolved Feb 01, 2026, 01:35 AM UTC

    The issue with Connections API has now been resolved. Departure dates on or after 1/31/2026 in Connections API - Cargo connections is now available for querying. Thank you for your continued patience and understanding.