twist3r wrote:I also have problems with routes. It's not a map problem because on the live map I could do the same route, but on the client I received the timeout. And it was only a 300km route ...
foxitrot wrote:dknight212 wrote:There are some areas not yet well mapped that will timeout easily.
Have you meant that seriously? If I understood you correctly, the routing server should possibly time out because of a hard-to-find route? This would be a manifestation of a really crappy communication protocol
CBenson wrote:Thank you. I thought I had dreamt the existance of this form as I could find the link to it.
invented wrote:CBenson wrote:I just want to reiterate that it is unlikely that waze support is closely monitoring this thread. If you are posting here, I hope that you are also actually submitting the form in the original post so that waze is aware of the extent of this problem.
How would they not be at this point?
deekster_caddy wrote:Today (Jan 2nd 2014) was the first time I tried Waze again, my daily commute to work, I-95 around Boston area was unable to connect to the routing server with several attempts on the way in, 8-9 AM EST. I'm able to connect now, while in the office at at work. In both cases I was able to use internet on the phone and download maps while traveling, notifications were working, but routing was not working at all.
Users browsing this forum: Yahoo [Bot]