Description
I am encountering an issue where replay files (.dem) are unavailable for matches occurred between 2026-03-09 and 2026-03-10. While match_ids are successfully retrieved via the publicMatches API, the corresponding replay files cannot be downloaded, and the parsing process fails to produce a valid .dem URL.
Steps to Reproduce
- Fetch recent matches using the
/publicMatches endpoint.
- Attempt to retrieve the
replay_url for these match_ids.
- Request a parse for the matches (if using OpenDOTA/STRATZ).
- Observe that the replay file is either missing (404) or the parse request remains pending/fails to locate the source.
Expected Behavior
The API should return a valid .dem URL once the match has concluded, or the parser should be able to fetch the file from Valve's CDN.
Actual Behavior
- The
.dem files are unreachable.
- Parsing requests do not result in a downloadable replay.
- Issue persists across multiple
match_ids from the last 24 hours.
Sample Data (Example Match IDs)
Match ID: [8721530888]
Match ID: [8721006601]
Environment
Additional Context
This seems to be a widespread issue for matches in this specific 24-hour window. I am unsure if this is due to a change in Valve's replay storage policy or a temporary downtime in the replay distribution network.
Description
I am encountering an issue where replay files (
.dem) are unavailable for matches occurred between 2026-03-09 and 2026-03-10. Whilematch_ids are successfully retrieved via thepublicMatchesAPI, the corresponding replay files cannot be downloaded, and the parsing process fails to produce a valid.demURL.Steps to Reproduce
/publicMatchesendpoint.replay_urlfor thesematch_ids.Expected Behavior
The API should return a valid
.demURL once the match has concluded, or the parser should be able to fetch the file from Valve's CDN.Actual Behavior
.demfiles are unreachable.match_ids from the last 24 hours.Sample Data (Example Match IDs)
Match ID: [8721530888]Match ID: [8721006601]Environment
Additional Context
This seems to be a widespread issue for matches in this specific 24-hour window. I am unsure if this is due to a change in Valve's replay storage policy or a temporary downtime in the replay distribution network.