[BUG] Match v5 - matchlist sends back older games despite startTime limit setp

[Chari49]

Hi, I've been trying to extract, for a few puuids, all the LOL games between beginning of S16 (determined as 8th Jan. 2026) and now.

I have used startTime : 1767826800, which is the timestamp, in seconds, of the 8th january 2026 00:00 GMT (server EUW).
Other parameters entered : No endTime, no queue, no type. Start = 0, Count = 100.

With those parameters, I was expecting a list of all games from 8th january until now, but the list is too big and includes games that are older than 8th january 2026. (I could go until 12 Feb 2025, so 1 year from now).
It is as if Riot was not considering my startTime, and was just giving me all games available.

Below image of the parameters used:

I confirm the result is code 200, my API key is up-to-date, I've tried on multiple puuids so it's not targeted to specific one.

It started to happen a couple of hours ago.

Or maybe I'm being crazy and using wrong parameters, but this was not happening to me previously unless mistaken.

Thanks for your help.

[MitchellRomney]

Can confirm this is also happening for TFT MATCH V1.

It's blocking us from our normal data fetching processes and summoner profile updating because each Summoner is returning hundreds of old results from many sets ago, causing us to hit rate limits instantly due to hundreds of unnecessary API calls for old matches.

[DarkIntaqt]

Did they switch back to milliseconds or did it just break entirely?

[Chari49]

I think it just broke, I tried both

[ethandouglas]

Confirming this is still broken on Saturday afternoon

[geozukunft]

For sure won't be fixed before Monday Eastern US time

[clong-]

Fwiw, it seems endTime is also not being respected. No matter what point in the past I set endTime to, I still get my most recent matches.