Ever since upgrading to 3.2 a couple weeks ago I've seen a huge increase in routing timeouts on my AT&T iPhone 4S. I'd say I get routing errors at least 50% of the time. My routes are short and aren't in areas that I'm unfamiliar with (just trips to and from work and family 5-50 miles away) but I wouldn't trust Waze anymore to route me through an unfamiliar area. It has become that unreliable.
Attached is an image from last night. As you can see, I have a good cell signal and I was still getting mapping and traffic data so there was a data connection, but routing server timeouts. Also notice the distance indicated to the next turn. The total length of this route was about 10 minutes, 4 miles.
Sometimes. It worked for a few hours randomly over the last few days. The Israeli weekend started Thursday evening, so unless people are working the weekend, I kinda doubt they actually fixed it. It's more likely that the servers aren't as loaded sometimes and are able to function properly.
The Waze infrastructure seemed to have more hiccups this morning during rush hour (7 to 10am GMT+8) in Malaysia. "Searching network" message appears even though the data connection is working fine and multiple users in Malaysia have also reported having the same issue, so this is not an isolated one.
Area Manager: Petaling Jaya, Malaysia. Waze Malaysia: FB | G+ | Forum | Wiki