Improve routing server system
Help customers by giving consistent, high-quality service through your routing server.
I am a long-time user of Waze and I live in Dayton, Ohio. In more than one quarter of my travels, Waze fails with a "routing server timeout" not just once each time, but repeatedly until I stop trying. Grrrrr.
The failure rate is even higher when I travel outside of the Dayton area. Please fix your service or redesign the routing server logic.
- On long trips, I have to select smaller subsets of my route in order to receive traffic-based guidance.
Then I have to enter the next subset of my route in order to receive traffic-based guidance, and so on toward my eventual destination.
- If you redesign your service you can avoid this bad level of service by doing just what I have to do (but you can do it within Waze's logic):
- Assemble and return the results from multiple subsets of the requested journey, with no failure and no annoying message to frustrate customers.
Anonymous
shared this idea
-
Anonymous
commented
Every time I use Waze from Albany NY to Long Island, the server times out. Suggestion is to break up trip. That’s ridiculous as there’s several options for travel and I need to know which way to go. Google maps has no issue. This needs to be fixed!
-
Jennifer
commented
It's annoying that the server times out and asks you to break up the routes.....I don't know where I am to break up the routes!! This is ridiculous! 😡