25 days ago
All my builds are failing i dont know why ive tried past bulids and thhey are also failing why is that
40 Replies
25 days ago
Your service builds in EU West (Amsterdam), and right now we have an open incident slowing down build snapshot uploads in that region: Slow build snapshot uploads in EU West. That is why your builds fail at the build step, and it is also why redeploying older builds fails the same way, since each redeploy runs a new build in the same region.
Your running deployment is not affected. We are still working with our storage provider on the fix, and once it is in place you can push a fresh deploy.
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Same here - and the builds that do not fail are failing on the deployment with this error:
The image "production-dpams.railway-registry.com/" could not be pulled from the registry. If the image is private, check that the registry credentials saved for this service are still valid.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Seeing similar issues, all builds failing with
Build Failed: build daemon returned an error < listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: raw-read unix @->/run/buildkit/buildkitd.sock: use of closed network connection" >
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
I am so tired of Railway's outages and how they're handling this. All they're saying is "We're sorry" and that's it.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Same here. "Failed to build an image. Please check the build logs for more details."
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
We are in EUW, the have errors in our region.
I think they need to compensate us.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
I'm so tired.. Railway has been so unstable lately, one outage after another, and now broken again
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
We're getting this error and build is failing
"Try redeploying, and contact Railway support if the same error comes back. The build failed while unpacking the base image, with an 'operation not permitted' error on a whiteout file, before any of your code was built."
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Railway more like Failway.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Genuinely like all they say is "We're sorry" and shrug it off without any consequences thinking this is acceptable. They're not going to compensate - if they didn't do it after 3 days of outage, they're definitely not going to do it for this either. I don't know what to do except for just abandon this "service" that can't do the most basic thing right. Just unacceptable
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
This is really unacceptable. We've been 7 days without a stable build pipeline: we can't merge, we can't ship, and we've already lost a client because we couldn't stand up a service for them in time. "We're sorry" on a status page isn't enough when the page shows most components green while builds have been failing for days.
Railway team: we'd still like a real post-mortem and a credit for the downtime. Several of us here are on Pro and paying for reliability we're not getting.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
This is really unacceptable. We've been 7 days without a stable build pipeline: we can't merge, we can't ship, and we've already lost a client because we couldn't stand up a service for them in time. "We're sorry" on a status page isn't enough when the page shows most components green while builds have been failing for days. Railway team: we'd still like a real post-mortem and a credit for the downtime. Several of us here are on Pro and paying for reliability we're not getting.
25 days ago
Indeed. But the funny thing is: "We're sorry. Three days of disruption to your production services, then the deployment and build failures after recovery, is a serious hit to your operations and your customers, and we understand why you're asking.
Hobby and Pro plans don't include service credits, refunds, or other compensation for platform incidents. Downtime credits are only part of the contractual SLA in Enterprise agreements, so there is no claims process for Pro workspaces, including for business losses above the cost of your subscription.
We're sorry we can't offer more than that."
So, you are a Pro user. Don't have Enterprise? No compensation for 3 offline days. Wow.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
lynxdabliu
Indeed. But the funny thing is: "We're sorry. Three days of disruption to your production services, then the deployment and build failures after recovery, is a serious hit to your operations and your customers, and we understand why you're asking. Hobby and Pro plans don't include service credits, refunds, or other compensation for platform incidents. Downtime credits are only part of the contractual SLA in Enterprise agreements, so there is no claims process for Pro workspaces, including for business losses above the cost of your subscription. We're sorry we can't offer more than that." So, you are a Pro user. Don't have Enterprise? No compensation for 3 offline days. Wow.
25 days ago
Let me get this straight.
Railway's pricing page says Pro is "For teams shipping to production." Their words.
Then production goes down for three days. Builds have been broken for a week. And the official answer is: "Pro doesn't include compensation. That's Enterprise."
So Pro is for production, except when production breaks, and then it's suddenly not their problem. 🤡
Meanwhile the status page showed Deployments: 100% for October while not a single person in this thread could deploy. "Slow snapshot uploads" is what they call every build failing.
This isn't a hosting company having a bad week. This is a company that sells you production and refuses any responsibility for it.
Railway, pick one:
- Pro is for production, so own your outages, publish a real post-mortem and credit the people you broke.
- Or Pro isn't for production, so change your pricing page and stop selling it as if it were.
Everyone affected: drop your failed deployment IDs and +1 this. Let's make it impossible to ignore.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
Let me get this straight. Railway's pricing page says Pro is "For teams shipping to production." Their words.  Then production goes down for three days. Builds have been broken for a week. And the official answer is: "Pro doesn't include compensation. That's Enterprise." So Pro is for production, except when production breaks, and then it's suddenly not their problem. 🤡 Meanwhile the status page showed Deployments: 100% for October while not a single person in this thread could deploy. "Slow snapshot uploads" is what they call every build failing.  This isn't a hosting company having a bad week. This is a company that sells you production and refuses any responsibility for it. Railway, pick one: - Pro is for production, so own your outages, publish a real post-mortem and credit the people you broke. - Or Pro isn't for production, so change your pricing page and stop selling it as if it were. Everyone affected: drop your failed deployment IDs and +1 this. Let's make it impossible to ignore.
25 days ago
The status page also confuses me.. The major outage from last week only shows up as 3 hours 52 minutes on builds whereas I think we all know it was longer than that?
What is this status page actually reporting off?
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
scottie-capturra
The status page also confuses me.. The major outage from last week only shows up as 3 hours 52 minutes on builds whereas I think we all know it was longer than that? What is this status page actually reporting off?
25 days ago
To be honest, I don't know.
Regarding your answer dalex, there's so much to ask for. 99.99% availability target but, when you have a problem that is outside of the 99.99%, well, "that seems like a you problem". The companies, like mine, that are trusting on Railway and have financial issues because of this problem don't get anything?
You're not talking about a simple outage. You're talking to a security issue that put everything on the line for us and for our projects.
So, the fault is not mine but my clients said that it is, indeed, my fault. I contacted Railway and the answer is nothing?
"Give us your money and when a problem appear, well, that's not our fault".
This is a company managed by kids that want to work as a PaaS. The problem is: they're playing with our safety, money and everything. A 3-day outage and security issues and zero actions regarding billing? That was not on my 2026 bingo so far.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
Railway
Your service builds in EU West (Amsterdam), and right now we have an open incident slowing down build snapshot uploads in that region: [Slow build snapshot uploads in EU West](https://status.railway.com/incident/QORAHHDA). That is why your builds fail at the build step, and it is also why redeploying older builds fails the same way, since each redeploy runs a new build in the same region. Your running deployment is not affected. We are still working with our storage provider on the fix, and once it is in place you can push a fresh deploy.
25 days ago
Any ETA when this will be done? Couldn't deploy last week, again today, this is terrible.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
adembacajdev
Any ETA when this will be done? Couldn't deploy last week, again today, this is terrible.
25 days ago
Pray for a miracle. At this moment, that's everything that you can do bro.
You're not getting any answer. ETA to be defined as always. The last one lasts for 3 full days.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
lynxdabliu
To be honest, I don't know. Regarding your answer dalex, there's so much to ask for. 99.99% availability target but, when you have a problem that is outside of the 99.99%, well, "that seems like a you problem". The companies, like mine, that are trusting on Railway and have financial issues because of this problem don't get anything? You're not talking about a simple outage. You're talking to a security issue that put everything on the line for us and for our projects. So, the fault is not mine but my clients said that it is, indeed, my fault. I contacted Railway and the answer is nothing? "Give us your money and when a problem appear, well, that's not our fault". This is a company managed by kids that want to work as a PaaS. The problem is: they're playing with our safety, money and everything. A 3-day outage and security issues and zero actions regarding billing? That was not on my 2026 bingo so far.
25 days ago
@scottie-capturra I worked out where your 3h52m comes from. The status page shows Builds at 99.48% uptime for October. October has 744 hours, and 0.52% of that is 3h52m. That's the downtime Railway is reporting for builds for the whole month.
Now compare it with Railway's own incident timeline (status.railway.com/incident/QH8L8B3E, labeled Major Outage):
- Opened Oct 21 07:24 UTC, resolved Oct 23 22:06 UTC. That's 2 days 14 hours.
- Pro builds were paused from at least Oct 21 09:28 until Oct 22 07:11. That's about 22 hours, and they kept "failing more than usual" until Oct 22 18:42.
- Hobby / Free / Trial builds were back only at Oct 22 23:22, about 40 hours in.
- The API wasn't fully restored until Oct 22 17:43, about 34 hours in.
3h52m on the status page. 22 to 40 hours in their own timeline. Both can't be true. So, to answer your question: the status page isn't reporting off reality.
And it gets worse:
- They knew three hours before telling us. Their preliminary report (blog.railway.com/p/preliminary-report-october-security-incident) says they halted build pipelines at 14:03 UTC on Oct 20. The status page only said so at 17:03.
- Pro was restored after Enterprise. Enterprise builds came back at 04:00, Pro at 07:11. So on the plan they sell as "For teams shipping to production", you wait in line while production is down.
- This was a security incident, not just an outage. The same report says encrypted environment variables were accessed and some were decrypted, potentially affecting up to 1.85% of workspaces. They haven't ruled out access to source code yet. Everyone who signed up before Oct 21 was told to rotate their keys.
- No final report date, no compensation. The follow-up comes "as the investigation concludes". And Pro gets nothing, because "credits are Enterprise only".
@lynxdabliu exactly. Our clients don't care that it was Railway's fault, they blame us. We carry the cost of their outage and of their security breach, and the answer is
"upgrade to Enterprise".
Railway, three concrete questions, and a "we're sorry" doesn't answer any of them:
- Why does the status page show 99.48% for builds when your own incident log shows Pro builds down for ~22 hours?
- When is the final security report coming? Give us a date.
- Why were Pro customers restored after Enterprise on a plan you market for production?
If you were affected, +1 this and post your failed deployment IDs. Thord, the harder this is to ignore.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
lynxdabliu
Pray for a miracle. At this moment, that's everything that you can do bro. You're not getting any answer. ETA to be defined as always. The last one lasts for 3 full days.
25 days ago
:S have anyone found any similar service that we can replace with? I was considering heroku or digitalocean
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
adembacajdev
:S have anyone found any similar service that we can replace with? I was considering heroku or digitalocean
25 days ago
tbh, idk. i'm looking for something too. @dalexhd any update?
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
@lynxdabliu @adembacajdev not Railway support, just another Pro user here lol. I moved my dev services from EU West to a US region (Settings → Deploy → Regions) and builds work there. Not a fix, but at least I can keep developing xd
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
@scottie-capturra I worked out where your 3h52m comes from. The status page shows Builds at 99.48% uptime for October. October has 744 hours, and 0.52% of that is 3h52m. That's the downtime Railway is reporting for builds for the whole month. Now compare it with Railway's own incident timeline (status.railway.com/incident/QH8L8B3E, labeled Major Outage): - Opened Oct 21 07:24 UTC, resolved Oct 23 22:06 UTC. That's 2 days 14 hours. - Pro builds were paused from at least Oct 21 09:28 until Oct 22 07:11. That's about 22 hours, and they kept "failing more than usual" until Oct 22 18:42. - Hobby / Free / Trial builds were back only at Oct 22 23:22, about 40 hours in. - The API wasn't fully restored until Oct 22 17:43, about 34 hours in. 3h52m on the status page. 22 to 40 hours in their own timeline. Both can't be true. So, to answer your question: the status page isn't reporting off reality. And it gets worse: - They knew three hours before telling us. Their preliminary report (blog.railway.com/p/preliminary-report-october-security-incident) says they halted build pipelines at 14:03 UTC on Oct 20. The status page only said so at 17:03. - Pro was restored after Enterprise. Enterprise builds came back at 04:00, Pro at 07:11. So on the plan they sell as "For teams shipping to production", you wait in line while production is down. - This was a security incident, not just an outage. The same report says encrypted environment variables were accessed and some were decrypted, potentially affecting up to 1.85% of workspaces. They haven't ruled out access to source code yet. Everyone who signed up before Oct 21 was told to rotate their keys. - No final report date, no compensation. The follow-up comes "as the investigation concludes". And Pro gets nothing, because "credits are Enterprise only". @lynxdabliu exactly. Our clients don't care that it was Railway's fault, they blame us. We carry the cost of their outage and of their security breach, and the answer is "upgrade to Enterprise". Railway, three concrete questions, and a "we're sorry" doesn't answer any of them: 1. Why does the status page show 99.48% for builds when your own incident log shows Pro builds down for ~22 hours? 2. When is the final security report coming? Give us a date. 3. Why were Pro customers restored after Enterprise on a plan you market for production? If you were affected, +1 this and post your failed deployment IDs. Thord, the harder this is to ignore.
25 days ago
Amazing analysis indeed and great thing to discuss about.
What surprises me is that you are not getting any answer to this questions regarding this. If you look closely, Railway is not a company that wants to know about the customers. Every single question is answered via bot on station. So, no human control regarding this. That's the first thing that surprises me. It's a start-up, it should be a little bit better on support.
Nevertheless, they don't care regarding anything.
A custom plan to have some trouble like march and october? Should we trust a company that gives zero to the customers for a outage that is Railway's fault?
Of course not. Pay your 20$ minimum and shut everything up (that is what Railway is thinking right now).
What a shame. It could be a great company but it's managed by some kids playing around and thinking that they are some entrepreneurs. You're not. Sorry to say that.
And regarding this problem, still no ETA. What a funny story to tell to our customers.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
@scottie-capturra I worked out where your 3h52m comes from. The status page shows Builds at 99.48% uptime for October. October has 744 hours, and 0.52% of that is 3h52m. That's the downtime Railway is reporting for builds for the whole month. Now compare it with Railway's own incident timeline (status.railway.com/incident/QH8L8B3E, labeled Major Outage): - Opened Oct 21 07:24 UTC, resolved Oct 23 22:06 UTC. That's 2 days 14 hours. - Pro builds were paused from at least Oct 21 09:28 until Oct 22 07:11. That's about 22 hours, and they kept "failing more than usual" until Oct 22 18:42. - Hobby / Free / Trial builds were back only at Oct 22 23:22, about 40 hours in. - The API wasn't fully restored until Oct 22 17:43, about 34 hours in. 3h52m on the status page. 22 to 40 hours in their own timeline. Both can't be true. So, to answer your question: the status page isn't reporting off reality. And it gets worse: - They knew three hours before telling us. Their preliminary report (blog.railway.com/p/preliminary-report-october-security-incident) says they halted build pipelines at 14:03 UTC on Oct 20. The status page only said so at 17:03. - Pro was restored after Enterprise. Enterprise builds came back at 04:00, Pro at 07:11. So on the plan they sell as "For teams shipping to production", you wait in line while production is down. - This was a security incident, not just an outage. The same report says encrypted environment variables were accessed and some were decrypted, potentially affecting up to 1.85% of workspaces. They haven't ruled out access to source code yet. Everyone who signed up before Oct 21 was told to rotate their keys. - No final report date, no compensation. The follow-up comes "as the investigation concludes". And Pro gets nothing, because "credits are Enterprise only". @lynxdabliu exactly. Our clients don't care that it was Railway's fault, they blame us. We carry the cost of their outage and of their security breach, and the answer is "upgrade to Enterprise". Railway, three concrete questions, and a "we're sorry" doesn't answer any of them: 1. Why does the status page show 99.48% for builds when your own incident log shows Pro builds down for ~22 hours? 2. When is the final security report coming? Give us a date. 3. Why were Pro customers restored after Enterprise on a plan you market for production? If you were affected, +1 this and post your failed deployment IDs. Thord, the harder this is to ignore.
25 days ago
If anything they should have retroactively made the outage time longer however they have seemed to make it shorter.. one can only speculate on why..
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
@lynxdabliu @adembacajdev not Railway support, just another Pro user here lol. I moved my dev services from EU West to a US region (Settings → Deploy → Regions) and builds work there. Not a fix, but at least I can keep developing xd
25 days ago
Yeah, I know but you could know any platform that is better than this kid-managed company called Railway.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
scottie-capturra
If anything they should have retroactively made the outage time longer however they have seemed to make it shorter.. one can only speculate on why..
25 days ago
Precisely.
But who cares: for Railway, you are a Pro user, don't have SLA. You can ship everything into prod but when you have a problem.... they made zero actions for the problems that they create.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
@lynxdabliu @adembacajdev not Railway support, just another Pro user here lol. I moved my dev services from EU West to a US region (Settings → Deploy → Regions) and builds work there. Not a fix, but at least I can keep developing xd
25 days ago
We violate our client contracts and govt regulations if we do this.. glad youre up and running (feeling pretty stupid for trusting all this for production right about now)
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Probably the best move, at least for me: open Claude and ask "move this to Terraform and AWS". xD At least I'd be paying for something with an SLA.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
@scottie-capturra I worked out where your 3h52m comes from. The status page shows Builds at 99.48% uptime for October. October has 744 hours, and 0.52% of that is 3h52m. That's the downtime Railway is reporting for builds for the whole month. Now compare it with Railway's own incident timeline (status.railway.com/incident/QH8L8B3E, labeled Major Outage): - Opened Oct 21 07:24 UTC, resolved Oct 23 22:06 UTC. That's 2 days 14 hours. - Pro builds were paused from at least Oct 21 09:28 until Oct 22 07:11. That's about 22 hours, and they kept "failing more than usual" until Oct 22 18:42. - Hobby / Free / Trial builds were back only at Oct 22 23:22, about 40 hours in. - The API wasn't fully restored until Oct 22 17:43, about 34 hours in. 3h52m on the status page. 22 to 40 hours in their own timeline. Both can't be true. So, to answer your question: the status page isn't reporting off reality. And it gets worse: - They knew three hours before telling us. Their preliminary report (blog.railway.com/p/preliminary-report-october-security-incident) says they halted build pipelines at 14:03 UTC on Oct 20. The status page only said so at 17:03. - Pro was restored after Enterprise. Enterprise builds came back at 04:00, Pro at 07:11. So on the plan they sell as "For teams shipping to production", you wait in line while production is down. - This was a security incident, not just an outage. The same report says encrypted environment variables were accessed and some were decrypted, potentially affecting up to 1.85% of workspaces. They haven't ruled out access to source code yet. Everyone who signed up before Oct 21 was told to rotate their keys. - No final report date, no compensation. The follow-up comes "as the investigation concludes". And Pro gets nothing, because "credits are Enterprise only". @lynxdabliu exactly. Our clients don't care that it was Railway's fault, they blame us. We carry the cost of their outage and of their security breach, and the answer is "upgrade to Enterprise". Railway, three concrete questions, and a "we're sorry" doesn't answer any of them: 1. Why does the status page show 99.48% for builds when your own incident log shows Pro builds down for ~22 hours? 2. When is the final security report coming? Give us a date. 3. Why were Pro customers restored after Enterprise on a plan you market for production? If you were affected, +1 this and post your failed deployment IDs. Thord, the harder this is to ignore.
25 days ago
And still regarding this: how much enterprise users do they have to say "move to Enterprise, you have SLA"? No Enterprise user is saying anything here... Weird, no?
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
Probably the best move, at least for me: open Claude and ask "move this to Terraform and AWS". xD At least I'd be paying for something with an SLA.
25 days ago
Yeah, but you are getting your billing account a lot more higher than Railway, no? I'm looking to Render but the costs... that's something that I have like: "is Render better than Railway to pay more?"
Because AWS and GCP can get a lot expensive if you do not have any control.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
I've see render terms, and on the pricing page it shows similar SLA contract terms... But, maybe it has better SLA than railway...
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
As far as I can tell, what we're all asking for is simple: Railway, please be transparent. The status page should reflect what actually happened, and every Pro and Hobby user deserves a direct message about last month's outages: what broke, why, and what's changing so it doesn't happen again.
You raised a $100M Series B in January saying you "believe in peaceful, powerful infrastructure" (https://blog.railway.com/p/series-b). Builds being down for almost a day is neither. I'd love to know how much of that round is going into build reliability.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
As far as I can tell, what we're all asking for is simple: Railway, please be transparent. The status page should reflect what actually happened, and every Pro and Hobby user deserves a direct message about last month's outages: what broke, why, and what's changing so it doesn't happen again. You raised a $100M Series B in January saying you "believe in peaceful, powerful infrastructure" (https://blog.railway.com/p/series-b). Builds being down for almost a day is neither. I'd love to know how much of that round is going into build reliability.
25 days ago
maybe you can create a thread with that and wait for railway support. while selecting, choose this one:
maybe you can have some answers for that.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
lynxdabliu
maybe you can create a thread with that and wait for railway support. while selecting, choose this one:  maybe you can have some answers for that.
25 days ago
@lynxdabliu I already did, and maybe that's the key point. I opened a private support thread with the full list of failed deployment IDs. The answer came from "Railway BOT": a well-written summary of the status page, "no workaround", "no ETA". Four follow-up questions later, still no human.
So that's the deal on Pro: you pay $20/month, you're told it's the plan "for teams shipping to production", and when production breaks you get a bot, no SLA, and no credits. To be fair, the bot was polite. But a polite bot isn't support.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
@lynxdabliu I already did, and maybe that's the key point. I opened a private support thread with the full list of failed deployment IDs. The answer came from "Railway BOT": a well-written summary of the status page, "no workaround", "no ETA". Four follow-up questions later, still no human. So that's the deal on Pro: you pay $20/month, you're told it's the plan "for teams shipping to production", and when production breaks you get a bot, no SLA, and no credits. To be fair, the bot was polite. But a polite bot isn't support.
25 days ago
Yeah, indeed! That's what I said: no human support. Railway does not give a damn for their customers. Even you and me, if we create a company like this one, you can do a lot more and be a lot more professional than this company is right now.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Now problems with US region... This could be a meme...
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
Now problems with US region... This could be a meme...
25 days ago
Try to migrate to EU West now. They saw some recovery, i saw it too. No more crashes during build/deploy.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Nothing….. they don’t take ANY responsibility on the issue I created with them privately. So, how many of you have decided moving away from railway? At least, I will wait tomorrow for their response regarding to this thread.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
Quick update from today, Oct 26 (UTC), for anyone tracking this:
- 11:05 – build snapshot incident starts in EU West. It has since spread to US West and Southeast Asia, and builds still fail early in EU West.
- 19:18 – new Major Outage: "TLS certificates not generating" for new or changed domains.
- Still open: "Recovery after October 21 Incident" (Monitoring), and station signups are paused.
On my private ticket, a Railway employee confirmed that four of my failures (Oct 20 api + workers, Oct 23, Oct 26) were builder stalls on Railway's side that no incident covers. Those never show up on the status page. They also confirmed that every API and project token created before the incident was invalidated on Oct 22, with no notice to customers.
Railway's answer on credits is no: on Pro, only Enterprise SLAs include them. Fine. In that case, two things cost Railway nothing:
- Put builder stalls on the status page, so we can tell your outage from our bug.
- Publish a reliability plan for builds with a date. Saying "we're working on it" every day isn't a plan.
Seven days without two clean days in a row. If you're on Pro and need to ship, plan a second region or a second provider. That's what I'm doing.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
Nothing….. they don’t take ANY responsibility on the issue I created with them privately. So, how many of you have decided moving away from railway? At least, I will wait tomorrow for their response regarding to this thread.
25 days ago
I doubt that they will respond to anything here. But I don't know... If you have any alternative, drop it here.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
dalexhd
Quick update from today, Oct 26 (UTC), for anyone tracking this: - 11:05 – build snapshot incident starts in EU West. It has since spread to US West and Southeast Asia, and builds still fail early in EU West. - 19:18 – new Major Outage: "TLS certificates not generating" for new or changed domains. - Still open: "Recovery after October 21 Incident" (Monitoring), and station signups are paused. On my private ticket, a Railway employee confirmed that four of my failures (Oct 20 api + workers, Oct 23, Oct 26) were builder stalls on Railway's side that no incident covers. Those never show up on the status page. They also confirmed that every API and project token created before the incident was invalidated on Oct 22, with no notice to customers. Railway's answer on credits is no: on Pro, only Enterprise SLAs include them. Fine. In that case, two things cost Railway nothing: 1. Put builder stalls on the status page, so we can tell your outage from our bug. 2. Publish a reliability plan for builds with a date. Saying "we're working on it" every day isn't a plan. Seven days without two clean days in a row. If you're on Pro and need to ship, plan a second region or a second provider. That's what I'm doing.
25 days ago
I'm planning another provider. This is getting absolutely ridiculous right now.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
18 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 18 days ago

