Project: bubbly-exploration (275ed4a2-8460-40c7-83cb-24349b212074)

Service: sivants-image-studio (6c9a263c-feb9-41b8-afe0-d33e8d92724d)

Environment: production (2dfd707d-075f-4536-8767-a64bfaf557ab)

Current stuck deployment: 96c5bf50-fcd8-4301-9f18-f35265055800

What happens: every deployment sits in BUILDING and the only build log line is

"scheduling build on Metal builder builder-mtwhnx". Nothing after that. Six deployments in a

row have done this over roughly 20 minutes. The API shows diagnosis: null.

What I've ruled out:

• Account is verified, not banned, no usage limits set or exceeded.
• Status page shows builds operational.
• Another project in the same workspace (sivants-api) built and deployed successfully today.
• Cancelled the earlier stuck builds and triggered one clean deploy of the latest commit.

Service config:

• Source: GitHub Badmrpotatohead/sivants-image-studio, branch main
• Root directory: services/background-removal (contains a Dockerfile)
• dockerfilePath: Dockerfile
• Health check path: /health
• Watch patterns: services/background-removal/**
• Variables: PORT=4858, BG_REMOVAL_HOST=0.0.0.0
• Public domain: sivants-image-studio-production.up.railway.app, target port 4858

Is builder-mtwhnx stuck or unavailable, and can this service be scheduled on a different builder?