builder-hbtvls rate limited by Microsoft Container Registry (MCR) — 429 on every .NET build
aocampol
HOBBYOP

22 days ago

Every deploy attempt for my service (chessclub-api) is failing because the assigned

builder "builder-hbtvls" is being rate limited by Microsoft Container Registry

(mcrprod.azurecr.io) with HTTP 429 Too Many Requests.

The error occurs during metadata resolution, before the actual image pull:

failed to authorize: failed to fetch anonymous token: unexpected status from GET

request to https://mcrprod.azurecr.io/oauth2/token?scope=repository%3Adotnet%2Faspnet

%3Apull&service=mcrprod.azurecr.io: 429 Too Many Requests

Affected deployment IDs:

- c071c74d-c335-4d27-b699-271e8ddf4287 (failed)
- e7e0491e-c239-472f-badb-a92141e2a895 (failed)
- f2d42276-5819-442e-b09c-fe6a8577d8d6 (failed)
- 3fdf6609-... (failed)

All four attempts were assigned to builder-hbtvls. The same build succeeded on

June 13 from a different builder. The issue is the builder's IP being blocked by

MCR — please assign a different builder for my next deploy.

Service: chessclub-api

Project: spirited-creativity (daf0ca46-51c6-44f5-b0ce-b56f2c737bc8)

Environment: production

Solved

4 Replies

Status changed to Awaiting Railway Response Railway 22 days ago


angeliqueln
HOBBY

22 days ago

Getting the same issue.

Screenshot 2026-06-16 065843.png

Attachments


Status changed to Awaiting Railway Response Railway 22 days ago


ponyogalante
PRO

21 days ago

Same problem

Screenshot from 2026-06-15 17-27-07.png

Attachments


jhazeair
PRO

21 days ago

same issue here --

2026-06-15T23:23:05.194658844Z [err] Build Failed: build daemon returned an error < failed to solve: mcr.microsoft.com/dotnet/sdk:9.0: failed to resolve source metadata for mcr.microsoft.com/dotnet/sdk:9.0: unexpected status from HEAD request to https://mcr.microsoft.com/v2/dotnet/sdk/manifests/9.0: 429 Too Many Requests >


ponyogalante
PRO

21 days ago

Solved


Status changed to Solved Railway 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...