a month ago
Hello, 3 of our telephony services that expose webhooks have been shutdown at approximately just before 7am this morning (2/11/2026); all other services remained running. Can we please know what happened? This caused us business disruption and we would like to be more resilient going forward. Thank you.
13 Replies
a month ago
Hey, there was an #🚨｜incidents that affected running deployments.
a month ago
Are your services running fine?
They are running fine now, but I had to restart them. Also, one of them is showing status as "Completed" (instead of the usual "Running") for some reason.
But even when they were down, they were showing "Running"; and what is worse, we did not get any Slack notifications when the services were shutdown, so the only way we could tell was from our BetterStack integration, but I think that makes sense: apparently the containers kept running, but our "python uvicorn" services inside the container got shut down; I do not understand why. Any help you can provide would be tremendously appreciated. I can provide log traces if needed.
a month ago
I don't have access to those services, only team members do.
Earlier today, an incident occurred that affected running deployments, taking them offline.
https://status.railway.com/cmli5y9xt056zsdts5ngslbmp
It is now solved and a post-mortem will be posted.
a month ago
Are your services healthy and running as intended after the crash?
Now, yes, but I only found out four hours later and had to restart each of them manually. How can I make this visible to team members -- is there a better channel to report such issues? Thank you.
Also, is there a way to put my services on auto-restart (at least for e.g., 3 attempts)? Thanks!
a month ago
Same here, all of my services look like they are online, but a few have been shutdown. I'm having to dig into each, then re-start! This is kind of ridiculous.
a month ago
I have an application using MySQL and it's still showing error 502 after today's outage. I've already restarted and redeployed it, but nothing has changed.
a month ago
Hello,
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.
Status changed to Solved medim • 28 days ago