#Our Services Were Shut Down Without Reason

12 messages · Page 1 of 1 (latest)

radiant viper
#

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.

clear coralBOT
#

Is this about a specific service? Linking one helps us understand your setup.

limpid jewel
#

Hey, there was an #🚨|incidents that affected running deployments.

#

Are your services running fine?

radiant viper
#
Railway

Railway is a full-stack cloud for deploying web apps, servers, databases, and more with automatic scaling, monitoring, and security.

Railway

Railway is a full-stack cloud for deploying web apps, servers, databases, and more with automatic scaling, monitoring, and security.

#

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.

limpid jewel
#

Are your services healthy and running as intended after the crash?

radiant viper
#

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!

austere portal
#

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.

Railway Blog

Railway experienced an outage caused by a misconfigured automated enforcement system that incorrectly terminated legitimate user deployments.