Hi ExpertFlyer Voice or anyone

The flight availability function does not return availability of SK8036-SK8041 flight operated by SQ. Is it a bug? or what is the reason behind? Thank you.

Hi VibeCentro - Sending you a PM with our findings.

When will seat maps show blocked vs taken correctly again? The issue has been ongoing for weeks now.

I keep getting this issue over and over when trying to create an alert for a specific flight.



The flight does exist, and I have a schedule alert for it, so I have no idea why it won't work...

Try without slash in alert name?

Hi Adam - This is unexpected. Our team will review and I will update you once we know more.

No. I have over 100 other alerts, all with a slash in the name, including the schedule alert for this same flight and aircraft change alerts for over 40 other flights in October 2025. This wasn't an issue in the old system or the new one. It's only this one flight.

Is there a timeline for fixing the inaccuracies presented in flight availability/seatmaps? For example:

This doesn't have anything to do with Expert Flyer. Actual seat reservations and inventory are separate things that mismatch all the time.

Until recently, this was not an issue with ExpertFlyer. In the example below, there are 7 or more J seats for sale, yet only 3 seats showing that are unassigned. This cannot be correct. But it would be correct to see 3 seats for sale, but showing 5 unassigned, which was common in the past.

My guess is there may be blocked seats. So either one of two things is happening:
1) Data sources (APIs, web scrapers, however EF gets its data) are no longer differentiating between blocked seats and occupied/assigned seats
2) Data sources are still differentiating, but EF logic/software is not differentiating and displaying properly

Sure, its probably blocked seats. EF has said "they are working on it". At the end of the day, if their GDS or data supplier cannot send block seat metadata, then there is not much they can do. My point is that often times GDS availability from an airline does't match up with seat reservations available for a host of reasons.

Agreed. I was more responding to the comment of "This doesn't have anything to do with Expert Flyer," which I am not convinced is accurate. Either they no longer get the correct data, or they do and are not processing it properly. Neither of which we know.

Hi WannaTheater, you are correct. Our data sources are no longer differentiating between blocked vs occupied for some airlines. We are working with them on this, but unfortunately cannot commit to a clear timeline just yet.

We pushed a fix for this today, you should be all set.

The flights on major airlines that weren't working (AC, BA) are at least now returning a result. Although for some reason it's inconsistent - e.g. the one I previously reported lists the aircraft as "Boeing 737 MAX 8 (7M8)", whereas other AC-operated flights just say "7M8". Same with AC327 YUL-YYC 9/11/25, which yesterday was also generating an error; it now works and returns "Airbus A220-300", while other AC flights say "223".

But it also appears that the new version of the site only returns one error when an aircraft change alert fails. For instance, with airlines like DM or SI that don't make seat maps available, it returns the same generic "Failed to create alert Please try again, if the problem persists contact support". Before the switch to the new site, it would reject the alert with a message that seat maps were not available for this airline.

I'm still not sure why a seat map is necessary when the flight schedule alert shows the type though...

(Although I'll note that the new site at least seems to have done away with the never-ending aircraft "change" alerts that were triggered by European carriers constantly adding or subtracting a row of intra-Europe business class, which is a very welcome change - I care whether the aircraft is a 223 or a 320, not whether AF is selling 3 rows of J one day and 4 rows the next, or vice versa).