Strange. It may be related to the other around-the-block errors that have been reported lately. Those seem related to some routing bug rather than a map problem or speed problem. I wouldn't think Waze would use the current speed directly when determining a route that is 50 minutes away. Maybe it does, but that doesn't make much sense. I would have expected Waze to look at how speeds are compared to normal currently and use that to help estimate what the speed will be when you get to that point based on how speeds are now compared to normal and then adjusting that to the historical speeds at the time you'll arrive. Kind of along the lines of -- If the speed right now is 5mph under the normal for this time of day and the historical speed for a road you'll be on in 50 minutes is 45mph, then adjust that down to 40mph as an estimate. Of course, that should also scale the longer it will be before you reach the area. So if it's 10 minutes away, it might adjust it down the full amount, but if it's 50 minutes away, it will adjust it by only 50% (2.5mph in this example) and if it's 2 hours away, adjust it by only 5% since current conditions compared to normal aren't likely to still be in effect in 2 hours. Those are of course just random numbers thrown out to give an idea of what I'm talking about. They aren't meant to be actual numbers to use. Maybe that's not a good way to do it, but I think it makes more sense than using current speeds directly if it's that long until you reach the location.