We're aware of these transient build queue issues and are actively working on improvements. This affects all plans, including Pro. We can't offer a specific ETA, but we recommend cancelling any queued builds and waiting rather than redeploying, as additional redeploys can compound the queue.

You are not aware of anything! There is no active incident reported about this! Are you trying to trigger your customers even more?!

The only service working reliably on Railway is their billing, my card surely get charged on time!

After 1hr and 30min of "Building image" the build finally failed with the message "Activity Heartbeat timeout"

The incident you linked was a separate build-and-registry issue from June 9 that has since been resolved. What you're hitting now is a known pattern where builds land on infrastructure without your prior build cache, which forces a full reinstall of dependencies and can stretch a one-minute build into tens of minutes, sometimes long enough that the build is cut off before it finishes. This is on our side, it affects all plans including Pro, and we're working on making build caching more reliable. While we work on it, the most reliable path is to cancel any queued or stuck builds and wait rather than triggering more redeploys, since repeated redeploys add to the load. We're sorry for the lost time here, it's genuinely frustrating and the frustration is fair.