Here too, with the same problem, I thought it was just me.

This continues to be awful over the past 2 weeks. Same here in multiple separate accounts and apps. It may be time to migrate off. If you can't rely on a hosting provider, they are failing at their primary purpose.

We are investigating an incident - you can follow updates here: https://status.railway.com/cmltkyu8905sl13amlju6j5yh

We hear you and take our responsibility seriously. I understand your frustration.

My databases have also been going down recently! I hope that I can continue using Railway, that y'all will figure this out.

Last week I lost data because of this. Luckily, my primary database is in Supabase, but otherwise it would have been catastrophic.

Yeah, I'm sorry, but today was the last straw. I'll be migrating off Railway. I've absolutely loved the build experience, and it's made CI/CD so easy, but that doesn't mean anything if almost every day my app is down in some way.

Continuing to say that "we hear you" isn't enough. I want to know exactly why Railway has been so unstable lately and what will be done to improve it. Until then, I cannot see myself using or recommending Railway.

To mitigate this going forward, we are planning two main improvements. We will deploy our TCP proxies across all hosts, and continue our ongoing work on the network control plane to eliminate any bottlenecks and introduce other improvements.

How long will it take to resolve this issue?

Hi all, the incident has now been resolved but if you are still experiencing any issues, please let us know and reach out. We're extremely sorry for all the inconvenience here, and assure you we're working hard to making a significant amount of changes to mitigate the class of errors that caused these issues.