Elevation profile appears exaggerated or incorrect

This issue started appearing 1-2 weeks ago
but like a month ago i had such a case too but by far not that extreme (50 km ~300m elevation diff vs actual)

[Förtha-Marksuhl](https://maps.openrouteservice.org/#/directions/50.938473,10.262213/Im%20Weihersfelde,Marksuhl,TH,Germany/data/55,130,32,198,15,97,4,224,38,9,96,59,2,24,5,192,166,6,113,0,184,64,70,0,24,3,160,9,128,54,83,79,192,102,0,104,5,97,32,78,26,0,224,5,128,118,26,6,226,44,161,14,205,72,48,99,75,145,86,92,186,49,111,156,155,54,92,57,177,17,201,155,16,116,64,64,0,234,158,4,68,216,114,128,5,229,0,45,174,124,164,117,238,129,0,25,188,0,54,233,115,128,9,230,13,210,0,115,0,90,43,8,0,87,68,84,100,36,109,16,71,116,103,116,104,116,68,48,79,60,100,200,43,43,20,216,116,88,16,0,95,66,160,0)

here in that example, you can see that there are at least 2 places that are at 0 elevation, thus here the calculation appears to be correct but the underlying data is not? on bigger routes you won't be able to spot that ....
makes this feature unfortunately useless at the moment :(

keep up the good work!

Reproduce the linked Förtha-Marksuhl route and inspect how its elevation profile is rendered and where the elevation values come from. Compare the displayed profile with the route's underlying elevation data, including the reported zero-elevation points; the issue is done when the profile reflects accurate source elevations.

Written by the indexing model from the issue text.