Justed checked and it is just 1 created route that it is not working on.

Hmm! Could you say what route that is?

Here is a screenshot.

Richard - that's https://cycle.travel/map/journey/114145 and doesn't work for me either.

Clicking the profile button fires off a request to https://route2-eu.cycle.travel/viaroute?output=json&alt=false&z=14&instructions=true&alt_graph=true&elevation_mode=2&loc=49.192383,16.611317&loc=49.184799,15.452662&loc=49.144012,15.002907&loc=49.003891,14.771229&loc=48.811855,14.315956&loc=49.440689,12.929643 which returns a 400 Bad Request HTTP error, with the JSON saying status 400 and status_message "no route found between points".

Ah – I can see the issue there!

The problem is that via point number 1 is on an unpaved section, but the route is set to paved-only. So cycle.travel fails to get the route while that point. If you remove via point 1 (or set the route to ‘paths & roads’) then it’ll work properly.

cycle.travel should certainly behave a bit smarter when this happens – it’s something I need to look into.