[BUG] Last match id is not at index 0 in the list returned by match history.

[befizal]

Bug Description
Match history randomly sends match ids in the wrong order (or the latest match ids are missing? didn't check), and often the service stops working ("service unavailable"). API URL: "https://europe.api.riotgames.com/lol/match/v5/matches/by-puuid/{{puuid}}/ids?start=0&count=1".

Problem Description
Same as "Bug Description".

Expected Result
The last match id should be at index 0 in the list (I suppose).

Actual Result
At first glance the last match id is not in the list.

Developer Impact
No impact.

• Frequency: Let's say after ~3 API calls (not 100% sure), and every subsequent calls.
• Severity: When I click "Last match" button, either the wrong match is showing up, or an error pops up ("service unavailable").
• Cost: 0.
• Efficiency: Situation gets back to normal automatically and randomly, let's say approximately once every day.
• User emails: No

Player Impact
No impact, personal use only.

Preconditions
No idea.

Repro Steps
Call the URL repeatedly (maybe).

[hectorgabucio]

Same thing happens to me. A lot of service errors, and some matchlists are NOT okay. For example, the summoner Piconator from EUW, the newest match id that I get from the match v5 API is from 14 days ago (a Lissandra game), but if I check opgg https://euw.op.gg/summoner/userName=Piconator he played 3 new matches after that game. Are matchlists still getting restored in EUW?

EDIT: I tried with match V4 and that endpoint has the newest matches, so I guess it is a problem with match V5

[RiotTuxedo]

We've resolved a lot of the 503 errors. Those should almost be non-existent now. The reconciliation work is still on going for League and TFT. We'll look into the matchlist being delayed and I'll get back to you.

[tisbells]

Closing out old issues. This was resolved. Feel free to reopen or comment if you feel this is in error.