25 days ago
Hi Railway Support,
My MySQL instance (Service ID: 10a76366-d7f2-4885-9ef8-efc493c30424/database?environmentId=d1a538eb-a6dd-4129-9e6f-30ff959029ff) is stuck in a "Starting" or "Transitioning" state and is currently unreachable.
This made my django application crash. Here are the logs for the datatabse:
My railway mysql datatabase:
2026-02-11T14:50:04.639381Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.4.5).
2026-02-11T14:50:09.921896Z 0 [Warning] [MY-010909] [Server] /usr/sbin/mysqld: Forcing close of thread 596528 user: 'root'.
2026-02-11T14:50:09.930389Z 0 [Warning] [MY-010909] [Server] /usr/sbin/mysqld: Forcing close of thread 596552 user: 'root'.
-------------------- content trimmed---------------------------------------
2026-02-11T14:50:20.531847Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.5) MySQL Community Server - GPL.
2026-02-11T14:50:20.531885Z 0 [System] [MY-015016] [Server] MySQL Server - end.
The database container is starting up or transitioning. Please wait a moment and try again.
1 Replies
25 days ago
Hello,
We had an incident earlier that caused deployments to go offline 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 inconveniences this has caused.
Status changed to Awaiting User Response Railway • 25 days ago
17 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 17 days ago