Problems we already know about, and what we are doing about them. If yours is here, there is no need to report it.
On a phone, the overview of all pages (/pages) is wider than the screen and you have to swipe sideways. We will make it scroll down instead.
Opening a route from a link sets the map to the region where the route starts. A route that crosses into another region or country is then partly outside that area, so places along that part are hidden until you widen the area yourself.
A climb counts on a route only when the route rides it foot to summit. When a route goes up and comes back down the same road, the direction check sees both passes on the same stretch and can read the ascent as a descent, so the climb is left out.
Hovering a climb row in the ride check ("along your ride") rings the climb's stored point, not its foot where the pin stands. For climbs whose stored point is not at the foot, such as Mont-le-Soie (about 3 km away), the ring lands next to nothing. The route drawer's climbs list rings the foot correctly.
The contract at /developers/api describes twelve endpoints. Two answer today: /v1/map-config and /v1/search. The other ten do not exist yet: the item-type catalogue, one item by id, coverage counts, regions and their best-of, the route list, one route and its GPX under /v1, and the write path for contributions.
A GPX still downloads from /routes/{id}.gpx, outside the versioned API.
The reference page now says how far along this is, counted rather than claimed, so the number here cannot go stale.
The country and region pickers on Regions and Get involved have not been tested with a keyboard alone. If Tab and Enter do not get you through them, that is this issue.
The climb profile of the Susten Pass is right now: the 10% descent that used to show inside the climb is gone. On the map, one short stretch of the line still switches from steep to descending and back. That is most likely an error in the elevation data, for example at a tunnel, and still has to be checked.
In the Surfaces view, a side road that OpenStreetMap has no surface for is drawn as red dashes, meaning nobody has recorded it yet. A main road without a surface tag, such as the N653 Viséweg in Moelingen, is still drawn as nothing at all, so ordinary tarmac can look like a gap in the road.
We plan to draw these roads in a light "probably paved" style.
Not what you hit? Tell us about it.
So we can tell you what happened. It is not shown to anybody, not even to curators.
Paste a screenshot with Ctrl+V (Cmd+V). Up to 3.
We will tell you what happened to it.