Routing timeouts

by **pjlasl** » Fri Feb 08, 2013 3:07 am

I am trying to get to a destination but it keeps failing saying timout server occurred. This is a 200+ mile drive. Is this normal?

by **txemt** » Fri Feb 08, 2013 4:19 am

by **pjlasl** » Fri Feb 08, 2013 4:38 am

That sucks...it appears they need to push out the timeout. What good is it to find the destination but not be able to navigate

by **AlanOfTheBerg** » Fri Feb 08, 2013 4:42 am

1000 miles is the limit, I think everywhere. I run into the 200 mile limit notice when doing add-a-stop.

by **txemt** » Fri Feb 08, 2013 4:47 am

pjlasl wrote:That sucks...it appears they need to push out the timeout. What good is it to find the destination but not be able to navigate

You comin to visit me and see how I knock out Waze?

by **pjlasl** » Fri Feb 08, 2013 12:07 pm

LOL...going to TN This weekend.

by **pjlasl** » Fri Feb 08, 2013 12:17 pm

txemt wrote:
pjlasl wrote:That sucks...it appears they need to push out the timeout. What good is it to find the destination but not be able to navigate

You comin to visit me and see how I knock out Waze?

Although this week it appears you are getting knocked out by river

by **su_A_ve** » Sat Feb 09, 2013 6:36 pm

Having problems too with long routes. Short ones are fine, but can't get a 300 mile route.

What's going on? Never had problems before with long routes. Using iOS 6.1 and latest waze client

by **pjlasl** » Mon Feb 11, 2013 6:10 pm

I just ranted about this LOL. I had my TomTom and it provided a 600 mile route in less time. Waze only routed once I reached 200 miles left on my trip.

by **pjlasl** » Mon Feb 11, 2013 6:11 pm

pjlasl wrote:I just ranted about this LOL. I had my TomTom and it provided a 600 mile route in less time. Waze only routed once I reached 200 miles left on my trip.

It appears Waze has a timeout of 30 secs...it should route faster than that...seems Waze needs to look at their routing engine