We are experiencing high response times for some airports, like IAD, ATL, and DCA. Our app’s timeout is 8 seconds; our flight data is basically none for the last 16 hours or so. We’ve tried to lower the howMany param to 25 in hopes of getting a quicker response, but that was a no go. Do you have an idea of when this will be resolved?
Thanks!
This is being worked on. For the short term the default howMany of 15 should reliably reside in the app’s time out value. However, this will require using the offset parameter to retrieve additional results.
The AirportBoards response times have been squashed back down to much more manageable values. You should be able to make large timely queries again.
It is awesome again, thank you!