Whilst debugging a routing issue using the default car.lua profile, I determined the cause was the use of the barrier=kerb tag on a node that is part of a major road. I believe the intention is for the barrier tag to describe the highway crossing, not the highway itself.

Here's an example:

node

diverted route

barrier=kerb is not included in the whitelist for the default car profile - the OSM guidelines treat the use of this tag for a highway crossing as a mistake.

However, it appears its usage is quite widespread, which leads me to believe a one-off correction would not prevent these from being recreated.

Whilst this is not specifically an OSRM issue and can be fixed with profile changes, it does raise the issue of how the profile can be more resilient to OSM tagging mistakes.

Related

There have been previous discussions around this topic.
#5067 - Routing over barrier=kerb may make sense over small private roads, e.g. driveways.
#3890 - Discusses changing whitelists to blacklists to deal with unexpected tags. This was applied for foot and bicycle profiles. The suggestion is this could also be applied to major highways for cars, where the list of applicable barriers is stable.