This morning I prepared my holidays. As I go to Switzerland, I try to find a route with the precise address. I 've got the answer that the server is not responding. I tested several destinations at differente distances and it seems that there is no problem up to 300-400 km, after, the server is not responding. Is it normal?
This is a known problem for a lot of long distance routing from north/west to east/south… The opposite direction should work, if our tests are correct…
Waze has been informed of this long lasting problem, but has not provided a solution yet.
That is an interesting something… since the problem is already existing for quite some time…
So, it would be nice to know more about what area you were leaving, what area you were going to, what version of the app and device, …
If we are talking about the same, it’s for sure not since the latest update… We reported the issue extensivly on 12 sept 2013, but it was already there for quite some time before that.
We had reports of this issue already in june, when people were also planning there (summer holliday) trip.
The route problem also happens to me. Routes very large causes server timing error. Do not know if it is worth mentioning, but the problem repeats on the site with the message “Whoa! Something went wrong. Please try again later.”
I think it depends on the amount of data the server has to send back to the phone. When it’s much, you need good connection, so at least 3G or Wifi and a certain amount of free RAM.
A few months ago I did some tests with multiple phones and noticed some diferences.
I confirm what you claimed: no real problem to calculate the route from Switzerland to Belgium. Back at home (Belgium) I tested to find the way back to Switzerland but without success.
Thanks to keep us informed about the possible improvment.
Up! At this moment i’m forced to use Google maps to do a trip of 600km to Germany. Even when I select a city on a highway (freiburg im breisgau) he doesn’t find a route.