22 days ago
my account has been paused for deployments, is there a current issue at the moment? or this is due to my plan?
23 Replies
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
mine too.. recently sucks to be in railway...
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
Hi guys? Any news? I've removed a current deploy thinking it would be a way to deploy again but now I Have any deploy up!!!! My customer is angry once the system is not working!!!!
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
We're sorry for the trouble. We're aware of an issue causing deployments to get stuck while initializing in all regions, and we're working on it. That's why deploys are paused right now. It isn't caused by your plan.
Removing a deployment won't get you around this. Once deploys are working again, redeploy your service (for example, use Deploy Latest Commit from the service's command menu) and it will come back online.
You can follow updates here: Deployments stuck in initializing
22 days ago
is there another resourceful and dependable hosting environment that it is easy to use as railway? this seems to be broken more often than not.
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
I was thinking of turning to pro thinking it was my plan, but it is a global issue. I wonder if is just railway or the rest of the hosting environments as well
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
Now every day there is an issue. our services serve a lot of customers. This is not a reliable service to use for real product
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
The active incident on the status page (https://status.railway.com/incident/Z1JDWW1W) does not mention "Deployments paused" - I also thought it was related to my plan. Minor feedback, but it will be helpful if you could update the incident to mention that - thanks!
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
The active incident on the status page (https://status.railway.com/incident/Z1JDWW1W) does not mention "Deployments paused" - I also thought it was related to my plan. Minor feedback, but it will be helpful if you could update the incident to mention that - thanks!
22 days ago
my shows this on the application Im working on in railway: Limited Access
Deploys have been paused temporarily
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
Getting quite fed up with this crap to be honest
Status changed to Awaiting User Response Railway • 22 days ago
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
"The peaceful way to ship software"
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
does anyone knows which other host environment works well with Visual Studio as easy as railway? wondering how easy it will be to migrate to new host environment
Status changed to Awaiting Railway Response Railway • 22 days ago
brody
We're sorry for the trouble. We're aware of an issue causing deployments to get stuck while initializing in all regions, and we're working on it. That's why deploys are paused right now. It isn't caused by your plan. Removing a deployment won't get you around this. Once deploys are working again, redeploy your service (for example, use Deploy Latest Commit from the service's command menu) and it will come back online. You can follow updates here: [Deployments stuck in initializing](https://status.railway.com/incident/Z1JDWW1W)
22 days ago
what is the estimated time to return, guys??? just a expectation to inform our customer!!!!!
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
Looks like deployments might be back
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
We can't give a specific ETA yet. The "Deploys have been paused temporarily" banner comes from the "Deployments stuck in initializing" incident, which affects deployments in every region. It has nothing to do with anyone's plan, so upgrading to Pro won't change it. The cause has been identified and the fix is still being worked on.
Services that are already running stay up on their last successful deployment. If you removed a deployment, use Deploy Latest Commit on that service once deploys are working again to bring it back online.
We're sorry for the disruption, and we know there have been several of these recently.
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
why is there an issue everyday what am i even paying for
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
brody
We're sorry for the trouble. We're aware of an issue causing deployments to get stuck while initializing in all regions, and we're working on it. That's why deploys are paused right now. It isn't caused by your plan. Removing a deployment won't get you around this. Once deploys are working again, redeploy your service (for example, use Deploy Latest Commit from the service's command menu) and it will come back online. You can follow updates here: [Deployments stuck in initializing](https://status.railway.com/incident/Z1JDWW1W)
22 days ago
would we get the railway up and running today?
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
It is back here!!! Thanks God!!!!!
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Open brody • 22 days ago
brody
We can't give a specific ETA yet. The "Deploys have been paused temporarily" banner comes from the "Deployments stuck in initializing" incident, which affects deployments in every region. It has nothing to do with anyone's plan, so upgrading to Pro won't change it. The cause has been identified and the fix is still being worked on. Services that are already running stay up on their last successful deployment. If you removed a deployment, use Deploy Latest Commit on that service once deploys are working again to bring it back online. We're sorry for the disruption, and we know there have been several of these recently.
22 days ago
any discounts, compensation for all these issues that happen more recently now?
22 days ago
We're very sorry for the disruption the "Deployments stuck in initializing" incident caused today, especially for those of you with customers depending on your services and work that stalled while deploys were paused. We know this has come on top of several other recent incidents, and we understand why you're asking us to help make up for it.
We're sorry that we're unable to offer compensation or a credit for this incident. We know that's disappointing after the time and trouble it has cost you.
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
I have the same issue today, I'm a little bit tired of this issues related to deployments, I'm seriously considering other services or even including migrate all my projects to aws, I'm paying for a services which it does not work properly and I can't work with my clients projects.
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Open brody • 22 days ago
22 days ago
Thank you, that was a fast fix, much appreciated!! not moving to another hosting environment.......yet....lol


