It's been reported many times since the route was originally released. Given the route was supposed to have been updated recently, it's a fairly obvious issue and presumably a very easy fix that would take minutes. It doesn't give me much confidence that all these bug reports that we are making both here and in the ticket system are being recorded properly