Your three services in the Printed project are confirmed QUEUED. Your workspace is on the Hobby plan, and during periods of high demand, we may temporarily pause builds for Free and Hobby tiers to prioritize Pro/Enterprise workloads. Queued deployments will automatically process once capacity is available, with no action needed on your part. If you need to deploy immediately during these periods, upgrading to the Pro plan bypasses the deployment queue entirely. More details are in our docs on limited access pausing.

The pause is already 3h+ so I suspect this is a bug, rather than a load balancing... Also, I don't see the yellow "Build paused" banner in my Deployments menu, which docs suggest is shown when temp pause of builds is in effect.

Yep, this was a bug that has since been resolved. Sorry about that.

Nothing has been resolved here yet!!

We're aware of these transient build queue issues and are actively working on improvements.

15h later… still stuck at build queue :(

Couriousily, the https://status.railway.com lights all green and reads: "We're not aware of any issues affecting our systems.". This is a bit frustrating...

I have also created a new environment (staging2), a clone of my staging, and tried deploy there, but same problem -- my services are stuck in the build queue...

We're aware of these transient build queue issues and are actively working on improvements.

This now looks like a resolved issue, thanks!