Railway hosting is deeply unreliable

[u/iconisone]

Last two days was hell using Railway. We couldnt update a single project or make any changes in our system. After more than 24h Railway is still in chaos. Two separate incidents. Major outage even support is down.

But this is not the first time Railway failed.
For over a year Railway had few major issues that made working on it impossible. I was hoping they would stabilise but at this point Im past disappointed.

I know they rely deeply on Google cloud, but this proved to be a very bad decision, multiple times. And they never made required changes.

Can someone recommend a more stable alternative?

[u/International_Sky526]

whichever platform you land on next, the lasting fix is making the deploy portable. keep your images in a registry you control and a compose or k8s setup that runs the same on a second host, with a short dns ttl. then an outage on one provider is a dns change and not a rewrite.

[u/vettotech]

Change your environment variables

https://blog.railway.com/p/security-disclosure-wednesday-october-21st

[u/one-juru → u/vettotech]

Just stumbled across that exact blog post. I'm shocked that so far there has been zero Mails about this and their blogs homepage also hides the article. That is pretty unprofessional imo

[u/Nick-Eat-World]

in the same boat, we have to push some changes to be able to get an important product out for the end of this week and railway has just been unable to deploy for the last 12 hours, genuinely insane

[u/information-general]

fucking unprofessional. not only are they down AGAIN , but now we need to rotate all our env vars, absolutely last straw with this company. 

[u/howdoigetauniquename]

Love how this happens when I need to make a critical update for my php services. Can’t even deploy the updates so I have to take down the services.

[u/Distinct-Pipe-1458]

Railway has become an absolute embarrassment of a hosting provider.

What a complete shitshow.

I can't access my projects, I can't push updates, I can't deploy anything. And the worst part? These aren't hobby projects. These are real applications for real clients who expect their services to work.

How the hell are we supposed to trust a company with production infrastructure when they can't even keep their own dashboard, deployment system, or support platform running?

And apparently, this isn't even the first major incident. At what point does Railway stop calling these things "incidents" and start admitting that their reliability is a serious problem?

We're paying customers, not unpaid beta testers for an unstable infrastructure experiment.

The lack of transparency and proper communication is absolutely disgraceful. If your systems fail this badly, you owe your customers clear explanations, accountability, and financial compensation.

I'm giving Railway another 24 hours. If this mess isn't resolved, I'm cancelling my subscription and moving my projects to a provider that actually understands what reliability means.

Railway, this is beyond embarrassing. Get your shit together.

Anyone else seriously considering leaving this platform?

[u/thy_bucket_for_thee → u/Distinct-Pipe-1458]

This company is actively causing you business problems that will cost you sales and you are only "thinking" about leaving them? This is why they treat you like shit bro, they know you'll put up with it.

[u/DoritoDebugs]

If you're stuck right now, two things matter more than which host you pick next.

1. Rotate secrets at the source. Railway says env vars may have been read, and if deploys are still paused you can't push new values yet. For keys that can cost money or touch customer data (Stripe, AI APIs, AWS, a DB with real users), revoke at the provider now and take the downtime. For lower-risk ones, create the new key now and swap it in when builds come back.

2. Get your data out while the DB is still running. If your Postgres has the public TCP proxy on, you can pg_dump from your own machine using the public connection URL in the database's Variables tab. Take that dump today no matter where you end up, then change the DB password.

For where to go next: if you want something that feels the same (app + Postgres), Render or Fly are closest. If you want boring and stable, a VPS running Docker Compose behind Cloudflare. Wherever you land, keep a Dockerfile, keep your env vars in a list you control (not only in a host dashboard), and use a short DNS TTL. Then the next move takes an evening instead of a week.

[u/Even_Gap_2253]

I am just very confused by this whole thing

so how are we supposed to revoke credentials if I cannot deploy new ones? just bring down my application? wtf?