I'm going to reopen an archived thread: https://help.railway.app/feedback/maintenance-option-5f338d6b

Ideally, deployments should be done with zero downtime, but this is not possible 100% of the time. So what do you do when you need to stop traffic from coming in during a hairy migration?

The current answer in Railway is to remove the deploy and then traffic sent to your app will bomb out. This doesn't allow for any mitigation, say a maintenance page that states we're "doing thingz". I believe this is a somewhat significant drawback.

I will be employing the temporary remove tactic, for now, but I'm not a huge fan.