8 hours ago
Hi Railway Support Team,
I am writing to express my strong dissatisfaction with the performance of my services under my current Pro Subscription. I am paying over $200/month, yet my servers are experiencing severe performance degradation and latency spikes.
Upon investigating, it is clear that the bottleneck is caused by noisy neighbors on shared/virtual CPU and RAM resources. Whenever other tenants on the same host experience high traffic, my workloads are severely throttled and penalized.
For a paid customer contributing over $200 monthly, getting throttled due to shared resource contention is completely unacceptable for production environments.
I request that you look into this immediately and provide a concrete solution:
- Move my services/containers to a dedicated or less congested host node to eliminate CPU/RAM noisy neighbor issues.
- Advise on any specific configuration adjustments or dedicated resource options available to guarantee consistent baseline performance.
Please investigate my account resources and get back to me as soon as possible with a resolution.
Best regards,
3 Replies
8 hours ago
Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.
This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.
Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.
- Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
- Keep it private and close the thread - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.
Status changed to Awaiting User Response Railway • about 8 hours ago
Railway
Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly. This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community [bounty](https://docs.railway.com/community/bounties). Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly. **Opening it makes this entire thread public**, including everything already posted. Nothing becomes public until you decide. Use the buttons below. - **Open to the community** - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away. - **Keep it private and close the thread** - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.
8 hours ago
I want support rather than an automated response!!!!!!!
Status changed to Awaiting Railway Response Railway • about 8 hours ago
3 hours ago
This still looks like an application-level problem, so Railway support can't take it further, but the community can. The buttons below are still live: open the thread up as a public bounty after editing out anything sensitive, or keep it private and close it.
Status changed to Awaiting User Response Railway • about 3 hours ago
Status changed to Awaiting Railway Response Railway • about 3 hours ago
2 hours ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 2 hours ago