Lost database connections on 3 projects during an outage with no support contact; moved to Render, which is slower but more reliable.
63signal
114reviewsi
A score out of 100. Negative and mixed reviews take points off, and so does having only a few reviews, so a handful of glowing reviews can’t beat a product many people like.
29% Positive15% Mixed56% Negative
Customers love Railway for being very easy to deploy to, with simple pricing that suits side projects and small production apps.
What customers love, and what they don’tWhat customers noticed
Customer reviews (114)
Add your reviewShowing 42 reviews mentioning outages Show all
Railway is insanely fast to deploy with a nice UI, but security and reliability let them down; switching permanently.
Started on Railway because it was easy and cheap, but two years of outages and the breach handling are pushing them off.
Liked not thinking about infrastructure on Railway, but recent downtime is a blocker and they are looking at self-hosting.
After an earlier outage they moved their services from Railway to AWS. After the latest incident they cancelled their subscription, saying even the support page would not load.
On a 7-day Railway trial, could not deploy on day 3 and is not happy.
Their app got a big traffic boost from a podcast shoutout, but new users could not sign up and they could not deploy a fix because Railway deployments were down.
Cybersecurity worker says Railway was unreliable for six months before the env-var breach and is moving off.
Outages are common on Railway and the breach handling gave no proper notifications or dashboard warning.
They say Railway has had major issues for over a year and two incidents in two days left them unable to update projects. Even support was down, and they are asking for an alternative.
They needed to ship an important product and Railway had been unable to deploy for 12 hours.
Railway has had flaky uptime in recent months though the developer experience is nice.
Railway is cheap and easy but a couple of major outages took hours to resolve; moving off to AWS.
Runs services with 100+ users on Railway; outages are mostly builder-related and have not hit running workloads, but only non-critical services stay.
Loved the Railway developer experience over two years but left for a self-hosted VPS because of major outages every two to three months, sometimes six hours or more.
API credits drained despite usage limits after the Railway breach, and they could not redeploy for 30+ hours.
Revoked an OpenAI key before it was used, but says Railway has had too many issues and will use a better-known host for sensitive apps.
They had downtime during the Railway incident while they redeployed their app on DigitalOcean, and do not plan to return.
They describe a Railway outage running toward 48 hours with their availability dropping from 99% to about 95%.
They say Railway's status page claimed slow builds while deployments were not working at all, even on the pro plan.
Railway asked them to change exposed variables but they could not deploy a new build, leaving their service inoperable.
Solo founder's OpenAI and Anthropic keys were compromised; rotated them but could not deploy because Railway paused deployments.
Spent hours rotating keys after the Railway breach only to find the new ones leaked again; fixes would not deploy.
Production database down for hours with no way to restore or redeploy on a Hobby plan.
Many issues lately; says Railway is not worth the $200/month they pay and is moving.
Their Anthropic key was used by an unknown party after the Railway breach and deployments stayed down for 10-14 hours.
As a paying customer running client applications, they could not access projects or deploy during the outage. They give Railway 24 hours before cancelling their subscription.
They moved projects off Railway after the underlying GCP provider cut it off for about a day. They also saw services locking up and needed repeated restarts.
Railway's only downside for them is occasional downtime and outages.
Uptime has been really bad lately with no error logs; migrating to another host.
Common questions about Railway
What do customers say about Railway?
Customers love Railway for being very easy to deploy to, with simple pricing that suits side projects and small production apps. The main downsides are outages and a security incident that leaked environment variables, which left some users with abused API keys, long deploy blocks and little communication from support.
Is Railway worth it?
Of the 88 reviews with a clear verdict, 30% are positive, 15% mixed and 56% negative. The praise mentioned most is easy to use. The most common complaint is outages.
What do people like about Railway?
The praise reviewers mention most: easy to use (24 reviews), great value (11 reviews) and reliable (8 reviews). For example: Railway handles Node and Postgres with zero configuration headache and its built-in cron jobs work flawlessly.
What are the most common complaints about Railway?
The complaints reviewers mention most: outages (42 reviews), poor support (14 reviews) and surprise bill (6 reviews). For example: They describe a Railway outage running toward 48 hours with their availability dropping from 99% to about 95%.
What does the signal score of 63 mean?
It's how well reviewed Railway is, out of 100. Negative and mixed reviews take points off, and so does having only a few reviews: a service needs plenty of them, compared with the most-reviewed services here, to reach the high 80s and 90s. It's worked out from reviews only, needs at least 5 of them, and updates as new ones come in.
What are the specs of Railway?
Category: Cloud platform. Free plan: No.
Where do these Railway reviews come from?
114 are quotes from Reddit, each linked to the original. Customer reviews are checked for spam before they appear. Every review, written here or quoted, is read as positive, mixed or negative.
