LexisNexis Cirium incident
Service Disruption - Historical Flight Status API and Historical Flight Status Lookup (Resolved)
Resolved after 1 hour 56 minutes, affecting Cirium Sky™ APIs and FlightStats.com, on July 13, 2026.
On Monday, 13th July 2026 from 13:53 UTC to 15:49 UTC, customers experienced HTTP 503 errors when accessing the Historical Flight Status API and no data returned from the Historical Flight Status tool on FlightStats.com. We have addressed the issue and increased the database storage allocation, restoring normal service operation. This incident has been resolved and the service remains stable while we continue to monitor.
Affected components
Update timeline
- resolved Jul 13, 2026, 04:29 PM UTC
On Monday, 13th July 2026 from 13:53 UTC to 15:49 UTC, customers experienced HTTP 503 errors when accessing the Historical Flight Status API and no data returned from the Historical Flight Status tool on FlightStats.com. We have addressed the issue and increased the database storage allocation, restoring normal service operation. This incident has been resolved and the service remains stable while we continue to monitor.
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