AlanOfTheBerg wrote:Route length is something which can affect the road type which Waze will prefer to use which we have no influence over. At certain distances (I cannot recall specifics at this time), Waze will try to not route on anything less than primary street except to get you to one, and off of one near the destination. Longer distances and even Primary Street isn't preferred over highway/freeway. Your list of streets looks like highway or greater for the middle sections, which, again, should be fine for routing even for longer routes.
What is the total distance for your route B?
It's looking north of 30 miles for the preferred route and 23 or below for the Waze provided route.
Looking around, 285 / Hampden Ave should be Major Highway at the maximum (at-grade intersections) (editor is down so I can't see what it really is), and given the difference of distances I would not be surprised if the routing server doesn't even consider that when a much shorter freeway is available -- I believe this is what AlanOfTheBerg is suggesting. How close to 285 do you have to get before Waze agrees to allow you to go that way? Do you actually have to get off 470?
As for Waze appearing not to consider current traffic speeds and vastly underestimating the speed of I-25, do you leave at the very beginning of rush hour? Is it possible the streets near your destination really are flowing very well when you leave but very congested by the time you get that far? It's not supposed to work like that, and I don't see it myself, but if it would explain what you see that might help isolate your problem.