42 minutes ago
Two consecutive builds on service andrews-team (project carefree-possibility, production) failed during build setup with:
failed to solve: failed to load cache key: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/alpine/manifests/latest: 429 Too Many Requests
Deployments 80999677 and 7412d56f, both on builder builder-qyngsx, roughly 21:16Z and 21:23Z on 2026-10-09. Both failed within ~13 seconds, before npm install or any build step ran.
Nothing in our project references alpine — no Dockerfile, nothing in railway.json. The pull is coming from railpack's own tooling, and since Docker Hub rate-limits by IP, the throttled address appears to be the builder host rather than anything on our side. Other projects on that builder are likely affected too.
2 Replies
39 minutes ago
Both builds failed during setup on a Docker Hub "429 Too Many Requests" response, before any of your build steps ran. That matches an incident we are currently investigating where builds and deploys fail pulling images from Docker Hub, which you can follow at status.railway.com/incident/O3D8H5MZ.
Status changed to Awaiting User Response Railway • 39 minutes ago
19 minutes ago
Quick update: this is caused by an ongoing Docker Hub incident that's making image pulls fail. You can follow their updates here: https://www.dockerstatus.com/incidents/01M4HA1E00AH6NXA276AW0CK2V
Once it's resolved, redeploying should go through. We'll let you know here when pulls are working again.