OSRM does not route properly through crossing http://osrm.at/1y3.
Probably the reason is applying role "via" in routing relation "only_straight_on" not on node but way. The tagging in OSM database seems to be used correctly but routing algorithms do not include such situation.
Another routing service provides correct driving directions.

OSRM does not route properly through crossing http://osrm.at/1y3.

Probably the reason is applying role "via" in routing relation "only_straight_on" not on node but way. The tagging in OSM database seems to be used correctly but routing algorithms do not include such situation.
Another routing service provides correct driving directions.