3 ms·
Unfortunately we had to make emergency migration off to Azure yesterday due to this. Thankfully our DB was not hosted on Railway and we were back up in a couple
by majdalsado 4mo ago
Unfortunately we had to make emergency migration off to Azure yesterday due to this. Thankfully our DB was not hosted on Railway and we were back up in a couple hours.
As much as we loved the simplicity they provided us, there's just been too many mishaps and shortcomings for us to continue running a B2B enterprise app on their infrastructure.
Sad day :(
- gandreani 4mo agoAzure suspended your account as well?
- jmaw 4mo agoI think they meant that they migrated off of railway TO azure as opposed to FROM azure
- jmaw 4mo agoWhat were your reasons for going with railway in the first place? I'm not super familiar with them, but did you choose them for unique offerings, or essentially just VMs? If unique offerings, how rough was the migration out?
- pocksuppet 4mo agoRailway can probably sue Google for their loss of income from you. Should be fun.
- binarycleric 4mo agoUnlikely to be successful. GCP and AWS have pretty tight terms of service and you're legally SOL unless there was true negligence. Accounts rarely get suspended for no reason. There is likely more to this story that Railway isn't sharing.