Same here. Pushed two new commits to two separate GitHub repos and both deployments got stuck in initialization for over 20 minutes. One of them is frozen at "Taking a snapshot of the code..." and never progresses past that stage.

This is becoming a recurring pattern. Almost every day there's some kind of build failure, stuck deployment, or unexplained freeze. At this point it's impossible to rely on Railway for anything production-critical.

Is there any status update or ETA for a fix?

Thanks for flagging this, and sorry for the disruption. We have an active incident affecting deployments right now, builds and deploys are slow to go out due to an issue on our build machines, and we're actively investigating it. This is on our side, not your repo or configuration.

You can follow live updates at https://status.railway.com. Your already-running services stay up in the meantime; new builds and deploys may sit in initializing until this clears. Once the status page shows the incident resolved, re-trigger your deployment and it should go through. We'll get this fixed as quickly as we can.

It resolved but now it is back, I have one for 10 minutes not even intialized.

Weird new commit is now going so i removed the stuck one

Glad that cleared up. Removing the stuck build was the right call, and cancelling queued builds before retriggering is the best way to avoid compounding delays if it happens again.