Routing server blips?

Can anyone suggest a reason, if they know of issues in the past, or currently reason for a couple of routing / navigation issues.

Turn Instructions
I’ve seen several reports that show a ‘Waze provided route’ but does not include the turn icons given to the user. Now I’m wondering if this was due the routing server not giving correct info to the client. This UR suggests they were given incomplete instruction (missing the road name).

Ignoring Restriction
On a similar theme, ie routing, several URs around St. Pancras show Waze routing down a restricted segment, set up correctly, and again no turn icons are displayed on the suggested route.

Could these be linked in some way when the routing server was distracted, I can’t tell you how old these URs are as they are not displaying the submission date for me.

For the first one, it has popped up in a few other places around the world. I have not yet read anything substantial however to say why or why not certain UR’s contain turns and why others don’t.

For the second one, for what time(s) is the restriction set?

The A5002 - St. Pancras Rd has a B>A restriction for All dates, All day, Some vehicles ( Taxis allowed) so this appears to be set correctly.

Unless these users have their App vehicle type set to Taxi & have forgotten then there is no reason for Waze to direct along this segment.

Nope, for that one I am in the dark. I will try to remember to take another look later to see if anything else may pop out at me D=

There are many regular examples of Waze routing users along bus/taxi-only segments and turns. The bus/taxi-only right turn from Commercial Rd into Whitechapel High St seems to generate new reports every couple of days.

It does make me wonder whether the new version of the app allowing users to set themselves as taxi- or private-drivers randomly set them as one or the other rather than defaulting to private.

Sent from my Galaxy S7 via Tapatalk