Maybe it’s SnapChat routing - the route disappears before you’ve seen it! :lol:
The results from last week have now been broken down into daily graphical summaries.
The two routes returned are graphed out as red = fastest and blue = shortest. Where the graphs have a yellow background, the server failed to return any routes. The horizontal axes are marked off in hours.
The “Route Time” and “Route Distance” graphs show the calculated times and distances for the returned routes.
The “Server Response Time” graph shows how long it took the server to respond to the routing request.
Monday:
Tuesday:
Wednesday:
Thursday:
Friday:
Saturday:
Sunday:
Raw data for this test: http://chizzum.com/lmr/test6.zip (427MB archive)
(Not adding to addressing the subject), but thought I’d chime in and say a big thank you to those involved in this investigation. It looks like a good piece of investigation work, and that Twister-UK probably enjoyed setting up this test!
I’m very into the investigative fault finding work, and am glad to see people with better skills sets than mine working within the community in their spare time!
Chris (twister) has done fantastic work on this as well as keeping various scripts up to date with numerous coding changes from Waze. Without his work the UK Waze map would be a lot less complete.
Waze HQ have done some further work and would like to know if it’s had any impact.
Please can you report below any further issues with routing in London, please specify the origin and destination and the day and time you tried. If you don’t want to publicly state the addresses then please send me a private message.
Just now tried to get a route from Hendon, NW London to a Kingston upon Thames postcode and it fails. If I use the town name rather than postcode, I get a route but the alternatives stop short of the destination flag.
Time and date as per post, 7:45 Monday morning.
I’m really not surprised. Very sad face.
Almost halfway through this logging session, and plots of the Monday-Wednesday results are available above…I’m not saying this set of results is identical to those recorded last time, merely that they’re sufficiently similar to make me question whether it’s worth the time and effort to generate new daily plots that you’d need to compare side by side with the previous set in order to spot any real changes.
So as has been hinted at by the posts above, seems like as far as London routing is concerned, it remains situation normal, all f’d up - unsurprise, unsurprise. Unless there are any radical changes in routing performance over the next few days that would justify doing some daily plots, I think I’ll just wait for the full weeks-worth of data to be collected and then do a few comparison plots to show how similar the two sets of data really are.
Chris - thanks, I’ve forwarded this on to Shira.
With all the weekday results now recorded from this run, time for a couple of quick comparison plots…
First up, routing failures. These are the regions in the previous daily plots that were shaded in yellow, here the previous run is shown in red and the current run shown in blue:
Spot the difference? Other than Friday morning, where this time around the server managed not to fall over at all, the rush hour responses throughout the rest of the week are rather similar.
And now server response times. Again, the previous run is shown in red, the current run in blue:
Ignoring the short-term variations and looking just at the longer-term shapes of these two plots, there’s again little to differentiate them.
So as far as I can see, this week has been business as usual for the routing server, despite whatever changes Waze have made. Raw data will be uploaded for them to ponder over at some point on Monday once the remainder of the weekend results have been captured. Let’s hope they can put it to some use and figure out another server tweak that results in some visible improvements this time.
Raw data for last week’s test will shortly be available at http://chizzum.com/lmr/test7.zip (404MB archive)
I’ve been informed that another fix has been applied. I hope this one works. Let us know if any problems.
Sent from my GT-N7100 using Tapatalk
I’m tracking a handful of routes across London, and they’re all failing during the morning rush hour(s).
And the trusty old north-south route I’ve been monitoring in previous tests is also failing during this evenings rush hour - Error: 503|Could not find a route…
Captured some data between 01:00 and 22:00 yesterday, which continues the trend of showing absolutely no improvement whatsoever over earlier tests - routing failed completely during the morning (07:19-09:05) and evening (16:34-18:30) rush hours.
Maybe one day…
Sent from my GT-N7100 using Tapatalk
Sooo… Nono, musn’t say that…! 
Just an update. There is no update. Waze are still looking at this.
Just to say that I have now experienced this myself. Well it wasn’t really in London, returning from Croydon area to Watford area, so all I wanted was a route round the M25. But just got nothing from Waze until a good 30 minutes into the journey. Evening rush hour.
Yep, that would seem to be normal behaviour in just the time we need Waze most. If I were a new user trying Waze out for the first time and that is all I got I would have given up a long time ago.