The flight history for
has an empty entry, that gives a 404 when selected.
They last two entries have the same start/end timestamps. Obviously there's something wrong in the database entries, but I can't check that. What I noticed on the frontend is that the history entry that works generates an API request to "api/tracks/?icao24=477ff2&time=1546534054" (correct start time), but the one that gives the 404 makes a call to "api/tracks/?icao24=477ff2&time=1546534070" (time is the _end_ time, not start).
Is what I'm trying to describe clear?
Attached is a screenshot with the current flight history.
Thanks for the report. We've noticed this bug, too. It's probably related with flights overlapping our historical and live data processing. The problem should disappear after a couple of hours as data gets post-processed.