Summary
Starting around April 29, 2026, matches played using Tournament-V5 codes are no longer retrievable via MATCH-V5. The tournament callback fires correctly (including a valid match ID), but requesting that match ID from MATCH-V5 returns a 404.
This appears to affect all tournament code matches across multiple independent tournament providers.
Reproduction
Create a tournament code via Tournament-V5 (tested with existing providers/tournaments that were working prior to April 29)
Play a match using the code (tested with full 5v5 and 1v1 vs. bots)
Receive the callback — match ID is included and looks normal
Request the match via GET /lol/match/v5/matches/{matchId} → 404
Region: NA
Last known working: April 28, 2026
First observed broken: April 29, 2026
Impact
This breaks the core workflow for community-run tournaments that depend on tournament codes for match verification, stat tracking, and result automation. Multiple independent tournament communities are affected — several have commented in the below related issue with their own match IDs.
We'd really appreciate any visibility into whether this is a known issue on the platform team's radar, or if there's something we can provide to help debug. Happy to supply any additional logs, codes, or callback payloads that would be useful.
Related
Reported in #828 (comments from late April/early May 2026), but opening separately for tracking since #828 covers many different Tournament-V5 issues over a long period.
Summary
Starting around April 29, 2026, matches played using Tournament-V5 codes are no longer retrievable via MATCH-V5. The tournament callback fires correctly (including a valid match ID), but requesting that match ID from MATCH-V5 returns a 404.
This appears to affect all tournament code matches across multiple independent tournament providers.
Reproduction
Create a tournament code via Tournament-V5 (tested with existing providers/tournaments that were working prior to April 29)
Play a match using the code (tested with full 5v5 and 1v1 vs. bots)
Receive the callback — match ID is included and looks normal
Request the match via GET /lol/match/v5/matches/{matchId} → 404
Region: NA
Last known working: April 28, 2026
First observed broken: April 29, 2026
Impact
This breaks the core workflow for community-run tournaments that depend on tournament codes for match verification, stat tracking, and result automation. Multiple independent tournament communities are affected — several have commented in the below related issue with their own match IDs.
We'd really appreciate any visibility into whether this is a known issue on the platform team's radar, or if there's something we can provide to help debug. Happy to supply any additional logs, codes, or callback payloads that would be useful.
Related
Reported in #828 (comments from late April/early May 2026), but opening separately for tracking since #828 covers many different Tournament-V5 issues over a long period.