Intermittent Timeout Errors on Flight Track API and Historical Flight Status API

Update timeline

1. investigating Aug 10, 2026, 09:04 PM UTC

   We are investigating an issue where some requests to the Flight Track API and Historical Flight Status API endpoints are returning intermittent timeout errors. Our engineering team is actively working to identify and resolve the root cause. Updates will be provided as soon as more information becomes available.

2. investigating Aug 11, 2026, 05:04 AM UTC

   We continue to investigate the issue affecting the Flight Track API and Historical Flight Status API. Our team is actively working on a resolution and will provide updates as they become available. If you have any questions or are experiencing this issue, please contact [email protected]

3. investigating Aug 11, 2026, 01:10 PM UTC

   Our engineers have restarted the affected database, and although an improvement in performance has been observed, some timeout errors are still occurring. Investigation of the underlying cause is continuing and a further update will be posted no later than 21:10 UTC. Thank you for your understanding. Please contact the Helpdesk if you require support.

4. monitoring Aug 11, 2026, 05:15 PM UTC

   The database instance upgrade has been completed, and service stability has improved. The Current Flight Tracks API is now operating normally, and the Historical Flight Status API also appears stable at this time. We will continue to closely monitor both services and investigate the underlying root cause. We will provide a further update by 05:30 AM UTC on 2026-08-12 with any additional findings. We appreciate your patience.

5. monitoring Aug 12, 2026, 05:33 AM UTC

   Following recent service improvements, the affected service is now operating normally. We are continuing to optimize performance across our platform to enhance stability and reliability. We remain closely monitoring all services and will provide further updates. Thank you for your patience and understanding.

6. resolved Aug 12, 2026, 11:31 AM UTC

   This incident has been resolved. All affected APIs are operating normally. Please contact the Helpdesk should you observe any ongoing performance issues.