23 days ago
Many of our services, including Postgres and Redis instances, were completely shut off without warning today due to the outages, even after the incident was marked resolved.
Check all your services to make sure they're still running, even if they are shown as "Online" in the canvas view. ‼️ The "Online" marker is inaccurate.
@ Railway staff - this is not the first time an incident was marked resolved when it really wasn't. Can we please have some more transparency going forward about outages and honest status updates? These outages affect thousands of our users. Thank you.
4 Replies
23 days ago
Hello,
We had an incident earlier that caused deployments to go offline 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
We are deeply sorry for the impact this incident caused.
I had the same issue (thankfully in my staging environment) and had to go search what hack was happening in my environment after my deployment to understand why everything was working, but Cloudflare was saying the server was “down”.
Not cool and didn’t receive any email to “check my services” or any report of the incident directly. Had to arrive here in the Discord to understand the issue.
Some of our services still cannot deploy successfully. I don't mean they're deploying more slowly; they're failing altogether.
23 days ago
i had the same issue earlier, after a redeploy my postgres worked.
Status changed to Solved brody • 18 days ago