I ran into some cases where the edge-based routing did not find a path close to the 'border' of the graph.

For example this: http://localhost:8989/maps/?point=48.250955%2C13.033712&point=48.252921%2C13.023304&locale=en-US&vehicle=car&weighting=fastest&elevation=false&edge_based=true&use_miles=false&layer=Omniscale
does not find a connection on bayern-140101.osm.pbf (for different algos dijkstra/astar ch/non-ch does not matter). With edge_based=false a route is calculated, but it is rather useless:

Not sure if anything can or needs to be done about this. The only thing that came to my mind is that we do a connectivity check in PrepareRoutingSubnetworks, but it does not pay attention to turn restrictions.