It wasn't just your imagination.

Oddly enough, the culprit was actually the WebFlyer server (you might have noticed that WebFlyer and InsideFlyer are still down ). Seems we have experienced a major hardware failure on that server and because the FlyerTalk servers were still making calls to the WebFlyer server it was causing FT to time out and crash.

To get FT back up and running, the tech team has delinked the two servers. As a result, some features, like the Airport Code Lookup, aren't working at the moment, but at least the site (FT) is up and running.