Not sure if i should put the project ID here or if its unsafe , cant make a private ticket because im not PRO , the workspace im admin on is on a PRO plan , but not me

Since you are only a project member, I will need a Project ID.

Thank you brody, its 7268d47f-eab3-4e5c-86db-ba143bfee27e

A hard limit was reached; your workspace admin will need to increase it.

Is there any way to solve this? im admin on the workspace too , can i update it myself ? the owner is sleeping and we are in production , this is causing us huge issues and there's no UI feedback or anything regarding this , we've been dealing with this for hours

You are not a workspace admin, nor are you a member of the workspace. Your workspace admin will need to increase the hard limit or make you an admin so you can increase it yourself.

I am admin on the the project, can you please try to not shut the project down at least for a few hours , until we can reach the admin of the workspace to update it

how comes we dont have any message or anything about this on the workspace

there should be some ui feedback at least

You are not a project admin. We don't have any notion of project admins. You are simply a project member with edit permissions.

Limit notifications are only sent to workspace admins, not project members.

Regarding not taking the services offline, I cannot raise the limit on behalf of your workspace admins; only they can do that.

Honestly? This is the moment I start looking for another provider.

Production went down 7 times today. And when I ask why, I get a permissions lecture instead of an answer to the obvious question: why does Railway take production services offline without telling the people running them?

"Limit notifications are only sent to workspace admins" so the people who operate the services daily are the only ones guaranteed to know nothing. That's a design decision, and it's a bad one.

On top of that, the only reason this ticket is public is that Railway doesn't offer private support unless you pay for PRO. So the options were: pay more to report the problem privately, or air it publicly. Here we are.

I'm the domain admin on my side so pointing my DNS at another provider takes me minutes. There's no lock-in keeping me here, only the quality of the platform. We both saw how that went today.

Appreciate the efficient reminder of where our workloads stand on your priority list.

All our limit systems are working correctly, firing on the set value and notifying the correct people. I'm sorry, but I cannot remove the limits for your workspace admins.

I understand this is not the outcome you are looking for, but it's all I can do for you here.

"All our limit systems are working correctly."

Zero autocritique and honestly, that's the one outage you can actually fix for free.

Zero notifications to anyone operating the services. And the official position is: the system is working correctly.

Limits firing silently is not "working correctly" it's working as designed, and the design is the problem.

Thanks for understanding genuinely appreciated how this was handled.

I asked why a platform that watches production go down can't tell the people it's happening to.

If anyone finds this thread in the future this is what you get as a railway customer.