This is server side issues globally, so cancel all queued so it can normal after sometime.

I'm having this issue on the free plan; if I upgrade to the Hobby plan, will deployments start working again?

Upgrading to Hobby likely won't fix this on its own — in my case this was stuck even after confirming an active paid plan, so it doesn't look like a plan/quota issue. It looks like a break in the GitHub → Railway webhook/build-trigger pipeline specifically, since deploying the exact same code via the Railway CLI (which bypasses GitHub entirely) worked fine for me while GitHub-triggered pushes stayed stuck in "Queued."

Here's the CLI workaround end-to-end if you want to get unblocked while the backend issue gets sorted:

1. Install the CLI:

   npm i -g @railway/cli

   
   (If npm blocks the postinstall script, run `npm approve-scripts @railway/cli` afterward.)
   

2. Log in:

   railway login

   If the browser-based login hangs or times out, use railway login --browserless instead — it gives you a URL + code to enter manually, which avoids a local callback port that can get blocked.

3. Confirm the CLI works:

   railway --version

4. Link the CLI to your existing project:

   railway link

   Pick your project, then your environment (e.g. production), then the specific service you want to deploy (not the database, if you have one).

5. Confirm the link:

   railway status

6. Deploy directly from your local project folder, bypassing GitHub entirely:

   railway up

   This uploads your current local files and builds/deploys them straight through Railway's backend. Watch the Deployments tab in the dashboard — you should see a new entry labeled "via CLI" progress through Building → Deploy → Post-deploy.

One caveat: this deploys whatever's in your local folder at that moment, not a specific git commit — so once GitHub-triggered deploys start working again, your next git push will take over normally and you can go back to that flow.

This got me a working deployment while my own ticket with Railway support is still open on the underlying GitHub-pipeline issue.

Change your region and try again