I think you will receive better quality help if you posted screenshots and a link to the OSM way in question.

Also, the very latest dev version of OTP has a much better way of visualising and debugging the street network.

I can confirm with Bond Street station on the Underground platforms using version 2.6.0. I have just done a survey there for the complete underground station mapping (the platforms are narrow so I mapped them as a way), but unfortunately it doesn't work with OpenTripPlanner.

The following is an example for Jubilee line northbound, with Naptan ID 9400ZZLUBND2 . Pedestrian routing from street to platform works as expected.

Note that the Elizabeth line routing works correctly on my server but it is because I am using an in-house feed for National Rail which directly takes position data from OpenStreetMap, instead of an external feed for the Underground services.

P.S. I am doing some postprocessing of data to circumvent the problem on Bond Street so you may not see the above bug on my server in the future. However, I have also mapped Chancery Lane station with the appropriate tag (the data pipeline should load the changes 2 to 3 days later), and it is impossible to circumvent this at a data level as the platforms are stacked, so I will leave this as the test case in London.

This has become a major usability issue for our journey planner in London for the underground. We have a number of narrow tube platforms (i.e. mapped as a way) which are directly under roads, and getting this wrong can cause unrealistic transfer times.

The following shows two itineraries involving changing between Moorgate (Northern City Line) and Liverpool Street (National Rail), one from Platform 9 and one from Platform 10. They are on the same level underground connected by corridors, yet OSM handles one properly, and the other is placed on the street.