Leaderboard where 90 beats 100

A small game service backs a leaderboard page. It has one endpoint that returns every player ranked from the highest score to the lowest, and the page renders that list top to bottom. Every player loads. Every name is right. Every score is right. But the ranking is upside down in a way that doesn't even look like a simple reverse. The board crowns a player who scored 90, while the two clear leaders — one with 110, one with 100 — end up stranded near the bottom. Scores like 8, 9, and 25 are scattered through the middle in an order that makes no numeric sense at all. Hit the endpoint directly and the same wrong order comes back, so this isn't the browser's fault. There are no errors and no failed requests. The data going in is fine and the data coming out is complete — it's purely the *order* that's wrong. Whatever's happening, it's in the one place that decides who outranks whom.