This issue affects all status products:-

Flight Info Direct - Status

Flight Info API - Status

Flight Info Alerts - Status

Status FVXML API

Status FVBatch API

Status FV Dynamic

Status FV FNB

Status Flight Leg Report

Root Cause: Last week, we identified an issue affecting a subset of Southwest flights where departure or arrival times had differing local and UTC dates. This was caused by a recent Southwest system change that impacted flight origination time interpretation, resulting in incorrect 24-hour delay indicators.

Resolution: Working closely with Southwest, we investigated and resolved the root cause. The fix was fully implemented at approximately 23:30 UTC on January 29, with data monitored and confirmed correct throughout the weekend.

Current Status: A small number of affected messages remain due to Southwest's early-processing queue, which generates messages up to a week before flight dates. Messages created and queued before the January 29 fix are still within the system. We are unable to purge these messages as doing so would remove both correct and incorrect messages.

Expected Resolution:

Affected flights are rapidly decreasing (expected maximum of 32 flights on Friday, February 6)
All early queue messages should be exhausted by end of day Friday, February 6 (UTC)
From February 7 (UTC) onwards, all data will be completely free from this issue

We apologise for any inconvenience this may cause and thank you for your patience and understanding.

OAG - undefined undefined

Southwest Flight Data Discrepancy