Hello Railway Support Team,

I’m experiencing a critical issue with my Railway MySQL service.

The MySQL service has been stuck in the “Deploying” state for many hours, and the database is currently unreachable. I have tried restarting the service multiple times, but the status never changes and the issue persists.

Important details:

- The MySQL deploy logs show that mysqld starts successfully and reaches:

“ready for connections”

- InnoDB initialization completes successfully

- There are no fatal errors such as data corruption or permission issues in the logs

- Despite this, the Railway UI remains stuck in “Deploying”

- My backend service cannot connect to the database at all

- Restarting both the MySQL service and the backend service does not resolve the issue

This behavior suggests that the MySQL container is running, but the Railway orchestration/health check is not transitioning the service to an “Active” state.

At this point, the database is completely unavailable and the service is blocked.

Could you please:

1. Investigate whether the MySQL service is stuck due to an internal Railway deployment or health-check issue

2. Manually reset or redeploy the MySQL service state if needed

3. Confirm that the attached volume and container state are consistent

This is blocking production usage, so any help would be greatly appreciated.

Thank you.