Hello Railway Support Team,

We are experiencing unexpected restarts on a MySQL service (version 9.4.0) in our Pro workspace.

The database starts normally and becomes fully available for connections. However, after a few minutes, it receives an external shutdown signal:

Received SHUTDOWN from user <via user signal>

This results in a controlled shutdown, but no deploy, configuration change, environment variable modification, or manual action was triggered on our side.

We have carefully reviewed the situation:

* No internal MySQL errors are present.

* No signs of OOM kill or resource exhaustion.

* CPU, memory, disk, and network usage are within normal limits (as shown in metrics).

* No recent image change or redeploy was initiated.

* This is a Pro account with sufficient allocated resources.

Additionally, we noticed the platform banner indicating ongoing deployment-related incidents, which may be relevant.

We urgently need clarification on:

1. Whether there is instability in the region hosting this service.

2. If an automatic restart or host migration was triggered internally.

3. If there is any active incident affecting stateful services or mounted volumes.

4. The specific reason a shutdown signal was sent to the container.

This database serves production workloads, so we would appreciate priority handling and technical insight into the root cause.

Looking forward to your response.

Thank you.