Can this one be reported too?
And also this one?
I’m not at all sure this can be ascribed to a glitch in the routing engine. The original comment that it could have been down to road speeds could well have been correct.
As for this one, there is no user drive provided at all and the waze-provided route, such as it is, shows no anomalies at all. It could simply be a destination problem: the reporter had arrived at their destination but Waze thought it was somewhere else and was trying to turn them around and send them else.
Here’s one which I haven’t been able to replicate in livemap, and where it can’t (or shouldn’t be, given the real-world nature of the junction) be explained by Waze thinking left-turning traffic could proceed any faster here than straight-ahead traffic.
And one where a right turn has been replaced with a left turn + u-turn…
I have an update from my continuing email conversation: 
So keep posting your examples here.
Please note that HQ only keeps drive logs for a couple of weeks. If you come across an example older than that, it may be worth posting it if it is a very clear example, but HQ won’t be able to do much about that specific case.
And, of course, we can now tell reporters that there is a recognised problem that is being worked on. 
Could this be another oddity? Anything we can do to help it?
I think this one is due to invalid speed data in your starting road. If you move the start point a bit further south it will take the correct route.
Look at the difference in times below just moving the start point a couple of yards north. Waze seems to think that if turning left out of Winchester Road the average speed is only 2 mph whereas if turning right the speed is 14 mph along the whole of the road. Obviously you don’t have to move very far up Winchester Road for the 12 mph difference in speed to make Waze prefer the right turn option.
Wait for some of the experts to take a look before you do anything but the simple answer here might be to just clear the speed data.
Thanks for looking Andy, how did you see the speed data?
I should have mentioned you can display the time taken in each segment rather than the speed. In my above examples the times are 11 seconds if turning right but 56 seconds if turning left, obviously as this is a single lane road the times are nonsense.
Thanks Andy, i’ve downloaded and installed the script, so i’ll have a look at it.
How would you clear the speed data for the segment(s)?
I’m not sure if I should tell you. :lol:
I’m only guessing here but as there there are no GPS points on the road and there doesn’t seem to be much speed data because changing times and days gives the same speed results therefore (and remember I could be completely wrong) it could be that there has only been one or two Waze users on the road.
It could be that a Wazer sat outside his house waiting for his wife to get in the car and had already got Waze running so when he turned left at the end of the road his average speed turned out to be very low, he might be doing the same thing every day. :roll:
You could delete the road and re-map but you may want to wait a couple more days to see if anyone else chips in because Waze may want the existing data.
In the meantime this makes interesting reading particularly the section halfway down about turn delays.
Ok Andy, thanks for the link, it does make interesting reading. I’ll hang on and see if anyone comes back with anything else.
Wondering if anyone can provide anything better than ‘it’s a quirk of Waze’ for this UR, before I reply to the user, as I suspect it’s another turn delay causing Waze to route people on a longer, but in it’s eyes quicker route. I haven’t been able to replicate the u-turn in Vicarage Cl.
Hi Atrophicshiner,
This looks like another one suitable for this thread, but while we’re here, you need to deal with this segment of yours… 
Simon
First off I have to state that I was in a terrible location for mobile signal and Waze was relying on it’s internal routing to plan a route from the Wirral down into the Midlands.
I was a little amused that Waze was suggesting I come off the M6 at J15 and rejoin at J14, but knowing how that section can be I wasn’t surprised (though surely the internal routing can’t take advantage of delays or segment speeds :?: ).
On closer inspection Waze wanted divert me off the direct (A5013) route to J14 and across to the A34, then instead of the legal turn onto the SB carriageway, go NB and make a u-turn at the next gap in the central reservation :!:
And… having a quick look at travel times to Luton Airport I would suggest even with the heavy traffic after J12, this suggested diversion isn’t any help at all and staying on the M1 would be less confusing :!:
