LexisNexis Cirium incident
HTTP 503 Errors on FlightStats Flex Historical Flight Status API
Resolved after 4 hours 43 minutes, affecting Cirium Sky™ APIs, on May 9, 2026.
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.
Affected components
Update timeline
- 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.
- 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.
- resolved May 09, 2026, 05:29 PM UTC
This incident has been resolved.
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.
Amazon Web Services