Still not able to connect to some deployed databases
profaile
PROOP

19 days ago

Since your big issue today/yesterday, I had to redeploy so many things, which now mostly work again. But we also have some databases that are Postgres High Availability. How do I redeploy that properly? Every single instance or what exactly? I don't see that you can redeploy the entire stack.

Also, btw: I think it is a shame that you mark this problem as "resolved" and don't notify us, but still half of my deployments don't work and I had to read through community messages to figure out that you have to redeploy everything.

Awaiting Railway Response

2 Replies

Status changed to Awaiting Railway Response Railway 19 days ago


sam-a
EMPLOYEE

19 days ago

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.


Status changed to Awaiting User Response Railway 19 days ago


sam-a

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. [We've published a post-mortem if you'd like more information on the incident](https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage). It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you. It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process. You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c Feel free to respond if your question has not been addressed.

profaile
PROOP

18 days ago

Our problem is that we have a high availability database and we are unsure how to redeploy it without wrecking it. Because there is no "Redeploy" of the entire database


Status changed to Awaiting Railway Response Railway 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...