Waze appears to only recognize NY Route 17 and part of CT Route 84 westbound. On the afternoon of August 3rd and on a prior trip 6 weeks ago, I drove to Ithaca NY from Orange, CT - a 4 hour drive. On the way to Ithaca, Waze gave me the fastest, most direct route, which included NY Route 17 and CT Route 84, but on the return trip, Waze suggested taking me WAY northbound, so 70 miles out of my way, adding 1 hour to my drive, but On the first trip in late June, I assumed that there must be some bad accident that Waze was directing me around. But yesterday, when I noticed Waze trying to drive me north again, I decided to run Google Maps in parallel to double-check. That’s when I noticed that the Waze version of my trip was 1 hour longer than Google. So I ignored Waze and followed Google Maps. As we drove, Waze kept recalculating, trying to get me to u-turn. It did this for 45 minutes at 65 mph, eventually suggesting a 7.5 hour total drive time! Finally, Waze app quit and closed. When I re-opened it, it refused to give me a map “Could not find a route”. I tested this by attempting to map to Westport, CT. Waze gave me a map this time, but suggested I drive north almost in the opposite direction, then back again along a nearly parallel highway, taking us 140 miles out of the way - CRAZY!! Finally, after crossing the Hamilton-Fisch Newberg Beacon Bridge eastbound, Waze finally was able to map again to Orange CT. In the end, Google Maps estimate was accurate. Serious issue along eastbound NY Route 17 and part of CT Route 84. It’s given me a serious crisis of faith in Waze.