Hey there! We've found the following might help you get unblocked faster:

• 🧵 Postgres down? Can't connect to [roundhouse.proxy.rlwy.net](roundhouse.proxy.rlwy.net)

• 🧵 Cannot Reach FastAPI Server

• 🧵 Can't reach database server

If you find the answer from one of these, please let us know by solving the thread!

Hello,

I have confirmed with our backend system that your database is fully accessible and that there are no further network issues on our side.

Thanks for checking it.

My Client is interested to know why did it happen and how to prevent it in future? Do you have any insight available for the root cause?

I'm sorry, but I cannot offer insights on this, as there have been no network outages on our end.

Thank you for checking.
For about one hour we had consistent errors that the server was unable to connect to the postgres proxy.
I have changed the postgres urls to the internal railway urls for our services and that seem to have resolved the issue.

Using the private network is indeed the best solution.

https://docs.railway.com/overview/best-practices#use-private-networking-when-possible