LexisNexis Cirium incident

HTTP 503 Errors on FlightStats Flex Historical Flight Status API

Critical Resolved View vendor source →

LexisNexis Cirium experienced a critical incident on May 9, 2026 affecting Cirium Sky™ APIs, lasting 4h 43m. The incident has been resolved; the full update timeline is below.

Started
May 09, 2026, 12:45 PM UTC
Resolved
May 09, 2026, 05:29 PM UTC
Duration
4h 43m
Detected by Pingoru
May 09, 2026, 12:45 PM UTC

Affected components

Cirium Sky™ APIs

Update timeline

  1. investigating May 09, 2026, 12:45 PM UTC

    We are currently investigating reports of HTTP 503 (Service Unavailable) responses affecting the FlightStats Flex Historical Flight Status API. At this time, the issue appears to be impacting a subset of requests to the historical flight status endpoint. Our engineering teams have been notified and are actively working to identify the cause and restore normal service as quickly as possible. We will provide an update on or before May 9, 2026 at 15:30 UTC, as more information becomes available. Thank you for your patience.

  2. identified May 09, 2026, 02:35 PM UTC

    Our engineers have identified the issue impacting the FlightStats Flex Historical Flight Status API and are actively working toward a resolution. We will continue to share updates here as progress is made. Thank you for your patience, and we apologize for the inconvenience.

  3. resolved May 09, 2026, 05:29 PM UTC

    This incident has been resolved.