hello

i am writing this before i leave railway, after having a terrible experience, and loss of thousands in revenue due to internal railway product failure, let me clarify - this is because railway's downtime and tech issues, AND how CS had handled this issue.

I would recommend you to escalate this to a the nearest CS director or VP level, as this is going to be published on many builder communities I am a member of , but let me be clear - this is not with the intent to cause RW damage or "avenge" my loss of revenue, but simply to warn other community members to stay away from railway if their apps and uptime is important to them, there are other VPSs out there with more stable environments. The warning won't be "beware of RW" style, it will be - sharing a case study, well documented, and how RW chose to handle it (and let me remind you - it was all caused due to RW down of service).

so,

here's the tech situation:

first - i had a downtime 3 about weeks ago, after redeploying n8n for upgrading its version - n8n suddenly stopped running a python node that used to work before. this was an internal railway failure, which later "fixed itself" without any changes from my part.

I did however, spent a few days to find a solution - on railway , on other communities, i even offered people to pay them to resolve this. interim, i have lost revenue of approx $5k, due to inability to display my n8n services to clients, which had caused me to lose a few projects.

you can see the original support request thread here:

https://station.railway.com/support/last-ticket-or-i-leave-748a30e8?utm%5Fcampaign=Community+Thread+Notification&utm%5Fcontent=Community+Thread+Notification&utm%5Fmedium=email%5Faction&utm%5Fsource=customer.io

and follow up on the events - how RW support turned its back on me, not helping at all.

second:

2-3 days ago - my n8n / postres/redis services crashed, wouldn't able to be re-deployed, this happened in parallel to RW service downtime.

i had to go over on the same above process to find a solution for it, for 2 days, not working, postponing clients, not onboarding others, and suddenly, after 2 days, the deployment started working.

i haven;t been using my n8n in the past 2 weeks, havent changed anything, but still - a downtime of 2-3 days, and suddenly, w/o any fixing from my side, it suddenly "fixed itself".

My plan:

Share the support threads + describe what happened exactly - present the facts as is, nothing subjective, and let the community decide for itself if this is the kind of service they would like to work with.

Personally, though it will take me lots of resources to migrate from RW to another VPS, I really had enough, with loss of service, lots of downtime, I cannot trust RW to host my business, and believe me, switching hosting is the last thing on my mind, never wanted to do this, but really, RW, and its support, have left me with no choice but to leave, angerly, disappointed, with a very bitter taste, so bitter, that I feel the need to actively share this experience with the world.

You can choose to pass this to the nearest CS director or VP , or throw it in the the bin, as you did with my support tickets.

I do expect a significant reimbursement, I will consult with my lawyer to see what's the next steps, but you can take action beore.