2 months ago
Hey everyone / Railway team,
I noticed something quite concerning regarding the Pro plan resource limits. Up until just 5-6 days ago, the maximum resource allocation per instance was clearly 32 GB RAM and 32 vCPU.
However, looking at the current limits and documentation, it seems it has been silently dropped to 24 GB RAM and 24 vCPU within the last few days. I actively monitor the changelogs and community updates, but I couldn't find any official announcement regarding this ghost-nerf.
In my current billing breakdown, I can still see traces of the 32GB/32vCPU capability, which makes this even more confusing.
For those of us relying on the Pro plan to run memory-intensive architectures—like MedusaJS, heavy Node.js background workers, or demanding database instances—that 8 GB difference per instance is a massive deal.
A few questions for the team:
- Was there an official announcement for this reduction that I missed?
- Why was this 1TB horizontal scaling math (42 replicas x 24GB) prioritized over single-instance vertical power without notifying the users?
- Will existing workspaces be grandfathered into the 32GB limit, or is everyone being hard-capped at 24GB moving forward?
Would appreciate some transparency on this. Thanks!
- Ümit
3 Replies
a month ago
looking for the answer by team
a month ago
yep they did this with no notice whatsoever
a month ago
Happened with me also, wrote about it on X and got a reply from product engineer at Railway:
> Hi, the new limits will only affect new customers, not existing ones. If you already had a Pro plan before the change, then your limits won't change until you cancel and resubscribe, or your payment fails. A blogpost explaining what changed and why is planned. We didn't nail the timing perfectly because there's a lot going on, which is why the limits were rolled out before the blogpost.