What is not down for you? Your whole account? People are experiencing an issue with postgres database that occurred @12h ago, which with most apps, would take them down completely.

I told someone else this, but I was able to delete my existing postgres and Railway detached the volume and left it floating. From there, you should be able to mount it to another service and write a small bit of code to tar that data and and present it for download.

Again, your mileage may vary. When you delete a service, I'm relatively certain that your backups get deleted as well, so if there is any other way around it I would take that.

In my case, I didn't have production data in place so I just killed it and re-ran migrations on a new instance. I did try to mount the original volume to a new postgres container, and it wouldn't load up; version mismatch or something (I think, I didn't care at the time to copy the error messages). Anyway, if you can get the volume detached the data should still be there.

Hello, thanks for responding. The data is not the problem (fortunately). My node service is just not responding. It's been more than 15 hours already and they are still down. How is this acceptable?

I had a lot of patience, but now I'm thinking it wasn't a smart decision to pay for Railway. It's a complete dissapointment, and I don't understand how is this acceptable.

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.

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.

Not working. It's not recognizing the last commit made on the branch, and I see no clear path torwards a solution. To make everything even worse, the deployments are just not working.

So sorry for the interruption. Everything should be running smoothly now. Let us know if a redeployment does not solve any remaining issues.