I'm having the same issue with Postgres across several of my projects. I've already followed the instructions, but the error persists. I'm going crazy her

I have the same exact issue

any news? My app is down for 9 hours now with no support answer. You guys posted all resolved messages and a post mortem, but for me no problems which started with your recent incident are resolved

I tried now to restart the service then redeploy it and the app was back online

I am trying this every hour for the last 3 hours. Nothing works.

I seem to be having the opposite issue. My new services are not sleeping. And there's one service that is standalone with no DB. It's been an hour and not sleeping.

Try CLI, new commit etc.

It's a database service so it comes from Docker hub, already tried multiple different tags. Issue persists. Really need somebody from Railway team to actually check out the logs I linked to.

So they are saying it is fixed on X but it is not actually fixed internally? Only experiencing the issue on one of my projects but conveniently it is the most important

yup, they keep telling everybody it is fixed and already published post mortem despite multiple customer threads posting the various db container connection issues

Btw I checked my old project and my site is running when I navigate and my mongodb connection is working (I see the network packets flowing), but both my services are sleeping in the UI, not possible since my website is working fine. Seems like they have an internal UI issue going on.

for me it's other way around as I posted, UI for db service says all online but logs clearly say it is shut down

Oh interesting. It seems like there's an issue in both UI logic and their backend logic. Wonderful.

I'M HAVING THE SAME PROBLEM! Nothing works, i've tried everything

Hello all,

We had an incident earlier that 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.

Quoting myself, did you actually read what I wrote?

Yes, I went through all projects multiple times and redeployed. Contrary to your status page and post mortem, your systems are clearly not working.

Is it fixed tho lmao that is what everyone wants to know.......

Hey folks, we're very sorry for the inconvenience. To answer the questions re: is it fixed? Yes, the underlying incident was resolved at the cadence described in the post mortem but in some cases, restarts were needed for certain services.

One quick note, if you have a DB and a service that relies on it and the set is failing, could you please try deploy the DB, ensure it's online and then try the service that relies on it?

re: the OP here, kremalicious, could you take a look at your mongod version? I'm seeing some logs mentioning:Wrong mongod version "UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion... which might be preventing Mongo from coming up.

Thanks for the answer. That mongod log also seemed important to me but not sure what I’m supposed to do, I use the standard mongodb service template provided by railway, already tried with some different Docker tags like 8, 8.20, latest. But all show the same error logs and shut down

Hello,

Looks like you were trying to deploy the wrong version of Mongo. I have deployed 8.0.10, and they are both online and running now.