All redis services in every environment in my project stopped with no indication that anything was wrong other than the logs.

This is a snippit from the logs:
```
1:signal-handler (1770821709) Received SIGTERM scheduling shutdown... 1:M 11 Feb 2026 14:55:09.289 User requested shutdown... 1:M 11 Feb 2026 14:55:09.289 Saving the final RDB snapshot before exiting. 1:M 11 Feb 2026 14:55:16.113 DB saved on disk 1:M 11 Feb 2026 14:55:16.113 Removing the pid file. 1:M 11 Feb 2026 14:55:16.221 # Redis is now ready to exit, bye bye...
```
We did not initiate this.
There is at least one other report of similar behavior from another user. Since it happened to all of our Redis services, it appears to be something widely initiated by railway.
It was not a deploy issue. We were dot trying to deploy redis and almost never redeploy that service.
We redeployed the redis service in our production environment and it is once again working as expected. I left the service as is in our staging environment so you can investigate. As you can see from the screenshot, the same sigterm was issued and the service stopped.
The only way we knew anything was wrong were the notifications that our app was failing to connect to redis.
We'd like to know what happened, how/why the sigterm was issued, and if this is something that can happen how are we to be alerted of these things in the future.

I'm tagging the specific redis service in production, but I have redployed that as I said. our staging environment in the same project is still experiencing the same issue and I haven't taken any action to fix it to allow you to investigate.