Thanks Mike.   I'm starting from Phoenix.   I drive this route weekly.   What is frustrating as well, is it originally tells you to take US-60 down to the 79 and go through Florence, back up through the 77.   

When I start my drive each week, it doesn't even give me the option to select the 60 (Through Superior) -> 177 -> 77 route.   I have to wait until I pass the 79, and drive several more miles before it finally gives up and redirects me through the 60 -> 177 -> 77. 

Again, while it's do-able, it adds about 20-30 minutes to your trip.   The fastest and quickest way to get from Phoenix to Mammoth is US-60 -> SR 177 -> SR 77.  

I don't know if the two problems are related, but for whatever reason, Waze doesn't see this as a possible route to Mammoth, which is not only wrong, but the preferred route to Mammoth.

Please let me know if you need any more info - happy to help.  
 

When I test a route starting west of your report, and the destination is Mammoth, AZ, Waze suggests the route you got...exiting to Kiser Street. The next turn is a right on Lobb Avenue, followed by a right turn onto SR-177.

While not ideal, and a little unexpected for other reasons, it seems like the route will work. The exit you're asking about is properly mapped and I can get routes using that exit.

You can see it testing the route in Livemap: https://www.waze.com/live-map/direction ... 1.17393459

So we can do a little more testing, can you give us an idea of where you are starting your route?

The two routes look to be about 11 miles difference and Google thinks they is only 7 a minute difference (checked there since Waze really doesn't want to offer the route you take).

There are things like the classification of the road that can play a role, as well as how direct a route is. If either route has spotty cell service, it can also affect routing as there may not be accurate speed data.

That you can think of...Are there any areas along the route where speed limits are missing or wrong?