Official wheel downloads return HTTP 403

I’m downloading—but not installing—Linux CPython 3.12 wheels for a separate machine, using Python 3.14 on Windows 11.

These four packages all return HTTP 403 from download-r2.pytorch.org:

  • torch 2.9.1+cu130
  • torchaudio 2.9.1+cu130
  • torchvision 0.24.1+cu130
  • triton 3.5.1

The attempt occurred September 11, 2026, at 05:47:52–05:47:54 UTC. Zero bytes downloaded. A separate cloud attempt also failed.

The URLs and hashes match the official package indexes. The attached receipt contains the exact URLs and errors. What is the supported way to retrieve these files?

receipt below

wheel-verification-receipt.json

{
“startedAtUtc”: “2026-09-11T05:47:52.164925+00:00”,
“scope”: “Four exact wheel files only; no installation or runtime validation”,
“manifestSha256”: “e61d8fa94e694b641fa27b26e5f07ec3914bfb9934bf898e9ae3e0337250ad70”,
“results”: [
{
“name”: “torch”,
“version”: “2.9.1+cu130”,
“url”: “https://download-r2.pytorch.org/whl/cu130/torch-2.9.1%2Bcu130-cp312-cp312-manylinux_2_28_x86_64.whl”,
“filename”: “torch-2.9.1+cu130-cp312-cp312-manylinux_2_28_x86_64.whl”,
“expectedSha256”: “e70e1b18881e6b3c1ce402d0a989da39f956a3a057526e03c354df23d704ce9b”,
“bytesDownloaded”: 0,
“byteVerified”: false,
“status”: “FAILED_NO_RETRY”,
“errorType”: “HTTPError”,
“error”: “HTTP Error 403: Forbidden”,
“httpStatus”: 403,
“elapsedSeconds”: 0.756
},
{
“name”: “torchaudio”,
“version”: “2.9.1+cu130”,
“url”: “https://download-r2.pytorch.org/whl/cu130/torchaudio-2.9.1%2Bcu130-cp312-cp312-manylinux_2_28_x86_64.whl”,
“filename”: “torchaudio-2.9.1+cu130-cp312-cp312-manylinux_2_28_x86_64.whl”,
“expectedSha256”: “a6c58d5e846da5a90d50bd425e2c24368747cd04297d95c6dd51d3f7f85fea26”,
“bytesDownloaded”: 0,
“byteVerified”: false,
“status”: “FAILED_NO_RETRY”,
“errorType”: “HTTPError”,
“error”: “HTTP Error 403: Forbidden”,
“httpStatus”: 403,
“elapsedSeconds”: 0.392
},
{
“name”: “torchvision”,
“version”: “0.24.1+cu130”,
“url”: “https://download-r2.pytorch.org/whl/cu130/torchvision-0.24.1%2Bcu130-cp312-cp312-manylinux_2_28_x86_64.whl”,
“filename”: “torchvision-0.24.1+cu130-cp312-cp312-manylinux_2_28_x86_64.whl”,
“expectedSha256”: “6939dd403cc28ab0a46f53e6c86e2e852cf65771c1b0ddd09c44c541a1cdbad9”,
“bytesDownloaded”: 0,
“byteVerified”: false,
“status”: “FAILED_NO_RETRY”,
“errorType”: “HTTPError”,
“error”: “HTTP Error 403: Forbidden”,
“httpStatus”: 403,
“elapsedSeconds”: 0.405
},
{
“name”: “triton”,
“version”: “3.5.1”,
“url”: “https://download-r2.pytorch.org/whl/triton-3.5.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl”,
“filename”: “triton-3.5.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl”,
“expectedSha256”: “8ce9bcedbd12b393d1309fb899e06818624c7e7765c5231ea5749850015c74d8”,
“bytesDownloaded”: 0,
“byteVerified”: false,
“status”: “FAILED_NO_RETRY”,
“errorType”: “HTTPError”,
“error”: “HTTP Error 403: Forbidden”,
“httpStatus”: 403,
“elapsedSeconds”: 0.394
}
],
“runtimeInstalled”: false,
“runpodActions”: 0,
“modelDownloads”: 0,
“providerCredentialsUsed”: false,
“bytesDownloaded”: 0,
“allFourByteVerified”: false,
“finishedAtUtc”: “2026-09-11T05:47:54.119893+00:00”
}

I’m able to download the wheels from the posted links onto my system. Could you retry it again?

I am trying to retrieve this official Linux ARM64 CPython 3.12 CPU wheel:

torch-2.13.0+cpu-cp312-cp312-manylinux_2_28_aarch64.whl

Official URL:

https://download-r2.pytorch.org/whl/cpu/torch-2.13.0%2Bcpu-cp312-cp312-manylinux_2_28_aarch64.whl

Expected SHA256 from the official index:
6f307c2c32d764ffc6ff6893b801fad6d4752f3e67966cb8abf1843427c02604

At 2026-09-16 14:35:16 UTC, one bounded diagnostic request returned HTTP 403 with the 17-byte body error code: 1010. No redirects occurred. The client was Python urllib on Windows, with no configured application HTTP/HTTPS proxy. No wheel payload was downloaded in that request.

The URL, filename and hash match the official index. Could you confirm whether this exact object remains publish

ed and advise a supported way to retrieve the same file, or whether the client-access policy needs correction? I have stopped retrying and have not attempted to bypass access controls.

I confirmed the wheel is still published and downloadable, and its SHA256 matches.
This doesn’t look like a missing artifact. The 403/1010 may be client/network/CDN-policy specific if you can reproduce it. Could you try to re-download it and report back in case you are seeing the same issue?