#Cannot connect to Postgres

16 messages · Page 1 of 1 (latest)

bronze fern
#

Wha'ts going on Railway. Please,,

lime questBOT
merry oxide
#

Hey, acknowledged! thanks for opening a help thread.
We were alerted and are working to resolve this now.

glad mountain
#

cc @bronze fern moving things over here

#

Going to clear out that chat a bit so anyone else with questions isnt flooded.

#

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!

#

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

bronze fern
#

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..

glad mountain
glad mountain
#

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

bronze fern
glad mountain
#

Ahh i think we're moving towards 5k a month then sorry about being a bit outdated on that :/

bronze fern
#

Got it, thanks for clarifying. Hope Railway can find a good way to bridge the gap between Pro and Enterprise.