Never mind. It updated the fourth time.
Failed to perform the action update/install. Error updating Home Assistant Supervisor: Update of Supervisor failed: error pulling image configuration: download failed after attempts=1: toomanyrequests: retry-after: 113.487µs, allowed: 44000/minute.
And a few minutes later:
Update of Supervisor failed: toomanyrequests: retry-after: 158.011µs, allowed: 44000/minut
And a few minutes later:
No supervisor update available - 2026.02.2
What’s happening?
Yes, it is happening to me. I cannot update several other updates until supervisor has been updated first.
Yes - seeing the same across three HAOS instances (on different WAN connections, so different source-IP).
My guess is a GitHub repository feels it is being hammered by updating HA installs, and is rate-limiting requests.
Now, whether this is a false-positive, or a mis-config of the HA update process is something only HA devs can tell. 
You are not alone. I’m also getting this error. I wasn’t able to update add ons Apps, and now I can’t update Supervisor.
@jhol-byte that issue seems to be unrelated to the above. It’s about a Core update failing due to internet connectivity, not a Supervisor update failing due to too many requests.
@everyone else, chill. Supervisor updates happen automatically (it’s the only part of HA which does this by default).
GitHub is getting too many update requests & throttling them. Leave it alone for a day or 2 & stop trying to force an update if the error already says there’s too many requests.
Ratelimits are occurring for the GitHub Container Registry, not the Docker Hub Registry. To fix this, you can follow the same guide as for using Docker Hub credentials for the supervisor, but with a couple differences.
ghcr.io under Registry. Head to Sign in to GitHub · GitHub and create a token with just read:packages checked only, then set an appropiate expiration date and name. Enter your GitHub username in the Username field, and in the Password field, put in your token. Click Add then try updating Supervisor/Core again!I also did the same for Docker Hub to avoid future issues. Just follow the guide, except don’t follow the screenshot on the docs, specify docker.io as the Registry, NOT hub.docker.com. Additionally, you can generate a token for usage instead of your Docker account password here: https://app.docker.com/accounts/burritosoftware/settings/personal-access-tokens. Set the scope to Public Repo Read-only (should be that by default), create it and set Username as your Docker Hub username and password as the token.
