We are currently experiencing some major weirdness with our database server. The issue is being investigated.
It has become apparent that something has gone very wrong with a recent database update done earlier today. The database is showing all airports as either "very old" or "to be included in future X-plane -release". Seeking a way to remedy the situation.
Turns out, this whole shenanigans with the database server is caused by ... "human error". One of the cache files that are used during the airport update was disabled during the database update mentioned above. This disabled cache file was supposed to track when a specific gateway airport was included and when it actually got released with some version of X-Plane.
Because of this, the data needs to be re-evaluated from the source data. This will take a while - unfortunately we can't just roll back to the old database contents.
At the time of writing, the update script is at ~37% of rebuilding the database. However ... until the update script hits 100%, the online database will not be updated ... because of this, site users are only seeing a single airport (which normally is not included on the site) at the moment.
At the time of writing, the update script is at ~45% of rebuilding the database.
At the time of writing, the update script is at ~80% of rebuilding the database.
At the time of writing, the update script is at ~96% of rebuilding the database.
The situation is normalizing... ;)
The situation has normalized.
In case you're interested, for each airport, it seems to take about 540ms for our backend system to
Naturally - if we knew that "nothing has changed", we could have had skipped quite a many of these steps. But since this time we didn't, we needed to "take the long route" to get "everything" on the same level playing field.