a year ago
My production Postgre database crashed by itself, causing disruption of my service. Why did this happen, why it did not re-deploy by itself, and how can I trust Railway that this won't happen again?
Crash happened at the pre-deploy step (deployment was triggered by Railway, not me).
ⓘ Deployment information is only viewable by project members and Railway employees.
3 Replies
a year ago
Hey Ivan,
We looked deeply into the logs and couldn't find where we would cause that redeployment. Are you sure that you didn't touch the region setting, for some reason we saw a request to move it to a different region.
- Angelo
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Hi Angelo,
yes, I am sure that I didn't touch the region settings. I did not make any deployments or changed any settings on that day!
This incident makes me uncomfortable - I switched to Railway from another service provider just because I wanted more reliability, and now Railway crashed my production database for no reason.
Ivan
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
There are no pieces of evidence internally that would allude to our systems triggering that redeployment. I am making the assumption that it was an accident or misconfigured setting. I am sensitive to your desire and needs for reliability, but I think this scenario won't happen again.
If you don't mind me asking, what provider did you switch from?
Status changed to Awaiting User Response Railway • about 1 year ago
7 months 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 • 7 months ago