Failures and edge cases

com.roblox.client · target ABI x86_64 · status page

Every non-200 this API produces, and what to do about it. Errors are JSON and always carry a stable error slug — branch on that, never on the prose in message.

{ "error": "not_stored", "message": "2.734.612 is tracked but no copy of it is stored" }
Status and slugMeaning and response
400 unsupported_abi You asked for an ABI this tracker does not follow. It tracks x86_64 only, and refuses rather than returning a build that will not install. Fix the request.
400 bad_version The version in the path is not shaped like 2.734.917 (or the word latest). Nothing was looked up.
401 unauthorized This deployment requires a token and yours was missing or wrong. Not retryable.
404 unknown_version A well-formed version this tracker has never seen. Usually a typo, or a build older than its history.
404 not_stored Known version, no copy kept — normally because it was pruned, or because it shipped no x86_64 artifact and was never worth archiving. Call /api/v1/android/files and pick something that exists.
404 not_found No such route. Check the path against Endpoints.
503 no_installable_build Nothing carrying x86_64 has been confirmed yet — a fresh deployment before its first full cycle, or a genuine run of arm-only releases. Keep whatever you have installed and retry later.
503 archive_disabled This deployment stores no files, so downloads cannot work at all. Metadata endpoints still answer. An operator decision, not a fault.
502 resolution_failed The upstream mirror could not be reached while resolving a URL. Transient. Retry with backoff.
500 internal_error A bug here. Retry once; if it persists, tell the operator which URL did it.

States that look like errors and are not

Retrying

Retry 502, 503 and network failures with exponential backoff — a few seconds, then a minute, then give up for this cycle and keep the version you have. Do not retry 400, 401 or 404; nothing about them will change on a second attempt.

A download that dies mid-transfer is worth retrying immediately: the redirect target supports range requests, so curl -C - resumes rather than starting over.

Is the server itself alright?

If answers look stale, check https://robloxandriod.com/healthz. It returns 503 when the poll loop has stalled, which is the difference between "Roblox has not shipped anything" and "this tracker stopped looking".

Stability of this API