18 days ago
Wha'ts going on Railway. Please,,
Attachments
15 Replies
18 days ago
Hey, acknowledged! thanks for opening a help thread.
We were alerted and are working to resolve this now.
18 days ago
cc @정인중 moving things over here
Attachments
18 days ago
Going to clear out that chat a bit so anyone else with questions isnt flooded.
18 days ago
Regarding your last message though about ent contract, we see this and are looking to see if we can find a middle ground.
I'm personally not happy that there are these reliability issues. The teams primary mandate is stability and ensuring that everyone is in a good spot here. So do know we're all working on it!
18 days ago
In terms of this current issue, the host your service is on looks like its in a nicer spot. Will update as I have any info
Yeah, I understand that the team is working on it, and I do appreciate that.
I think customers tend to get more sensitive when issues happen at the PaaS/infrastructure layer, because there is not much we can do on our side once that happens. Sorry as well if I sounded too harsh earlier.
After redeploying, things seem to be working fine now. I'll monitor it for a few more minutes. Do you know what the root cause was?
Also, I think something like AWS support plans as an add-on could make a lot of sense.
Our service is B2C and has around 250K DAU, but our Railway bill is still only around $300/month. To reach $10K/month, at least in Korea, we would probably need to become a service used by almost the entire country..
18 days ago
Oh absolutely, please dont feel sorry about being frustrated I would too. I'm here to bridge the gap between what we're doing and putting it across to you so hope I was able to do so <:bufo_pray:1331539894769684513>
18 days ago
For what its worth, our monthly enterprise agreement is $2k. Not trying to push you into something that doesnt make sense but want what works best for you.
18 days ago
For the root of what caused, checking in with infra to see what they say but don't have any info i can share yet. Still debugging fully
Hmm.. When I asked via email before, I was told that $2k would be difficult and that we would likely need to commit around $5k/month, which felt too high for us. What we mainly need is a less crowded host, and ideally an uptime SLA if possible.
Attachments
18 days ago
Ahh i think we're moving towards 5k a month then sorry about being a bit outdated on that :/
Got it, thanks for clarifying. Hope Railway can find a good way to bridge the gap between Pro and Enterprise.
It still doesn't seem fully stable yet on our side. Are there any other ongoing incidents or host-level issues here?
Attachments