Here is another slightly different example of what however seems to be the same underlying issue. In this case, Waze wanted me to do a left turn, go straight for a while, do a U-Turn, come back to the very same intersection and do another left.
All that instead of just going straight ahead.
Of course I assumed some editor had disabled the straight "turn" restriction, and checked as soon as I was home a few minutes later, but no. Straight ahead was "green". I also couldn't duplicate the phenomenon on the live map not even 30 Minutes later. I might also add that this was late in the night, where it is rather unlikely that Waze has good reason to have stored a high delay for the straight through at the intersection. Also, there was n ore-routing involved at any point on my whole route, this is what Waze had originally calculated right from the start. And at no time of the day *ever* this suggested route can even remotely be faster than just going straight.
So, either something's going severely wrong at the routing server itself, or something is storing/corrupting invalid speed data for segments or intersections in the waze database. At any rate, waze should seriously look into this ASAP. Such sort of nonsenic misrouting is not helpful to the acceptance of Waze.
Permalink: https://www.waze.com/editor/?zoom=4&lat ... TTTTFTTTTT