Hobby plan is $5 not $10 ;-)

are you trying to be funny? i have been trying to build a 3 PAGE tanstack app, the smallest app imaginable, for almost an hour and a half now. i had to PAY a 5$ invoice from 2 years ago when i hosted something else, for some reason, AND 5$ to start a new subscription (thus 10$), YESTERDAY, and haven't been able to deploy one thing yet. I just payed 10$. like driving up to a jackinthebox, paying at the first window, and driving away! lol . i apologize for even POSTING this, because I didn't know it was PUBLIC, but of COURSE, there is no way I can see to REMOVE it, so here it is. But I still cannot deploy ANYTHING it just sits there, and spins. And, I mean, I understand there are PROBLEMS with stuff somethings, but to just say you're PAUSING hobby build completely, with no estimated time whatsoever? do you not think that's lame?

and call me blind if you want to, I can't even find ANYWHERE on this site to CONTACT support. like PERIOD. I would LOVE to initiate a refund, as I have not USED the service at all, but cannot even find a link to CONTACT ANYONE about it

aaaaaaaand of course, i just cancel the build, delete the lock file and npm modules folder, reran npm install and the app worked. so just, please, file this away in my box of shame, and tar a feather me. PLEASE. i'm clearly a frustrated idiot.

When the build queue backs up during an incident, builds are paused in tier order to allow the queue to drain. That starts with Free and Trial, then Hobby, and Pro can be paused too if pressure on the queue is high enough; Enterprise keeps running. It's how capacity gets managed across the platform during incidents, not something Hobby-specific. Without that mechanism, the queue wouldn't drain, and the incident wouldn't end.

Put yourself on the other side. If your project grew to the point where it was handling production traffic on a higher tier, you'd expect your build to be served before a free-trial deploy. The same logic runs all the way up the ladder: Enterprise before Pro, Pro before Hobby, Hobby before Trial, and Free. It's the only fair way to allocate constrained capacity.

All plans resumed at 21:13 UTC, and the incident is resolved (https://status.railway.com), so a fresh deploy should go through normally (as you mentioned).

For the refund request, the path is https://docs.railway.com/reference/pricing/refunds#requesting-a-refund. Both the old outstanding invoice and the new subscription can be reviewed there.

You're already in touch with support; this thread is the channel for Hobby and Pro.