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

• 📚 Troubleshooting Slow Deployments and Applications
• 🧵 Railway proxy timeout
• 🧵 TCP Proxy for PostgreSQL not accepting connections - Connection timeout
• 🧵 502 Gateway issue, but my Postgres has space.

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

+1

+1

+1

After restarting the DB, normal operation is confirmed!

+1

After restarting the DB, it is fixed.

I had same issues.

I had same issues. How do I restart DB

After I restarted my db it's fixed

I got the same issue on our two projects. The database received a shutdown signal at 2:55pm UTC.

We got complains from our users, that's a mess.

Have you been able to sort it out now

@dammyjay restarting the server will fix it

I did a restart on my db and user were able to login and all pages were able to fetch information from the database. First were you able to load up and access all your tables on railway

As most of you noted, a restart or redeployment should fix the issue.

If any of you are still having issues please try restarting or redeploying your services. The incident yesterday caused some running workloads to be unexpectedly terminated while the status in the UI didn't properly update. This has since been resolved, but in some cases, you may need to redeploy your services.

You can find the post-mortem for the incident here: https://blog.railway.com/p/incident-report-february-11-2026

Our deepest apologies for the inconvenience this has caused.

If you do still have an issue, please open a new individual thread so we can troubleshoot any further problems.