Title: Multiple MySQL databases on Railway crash simultaneously and require redeploy

I am experiencing a recurring issue with MySQL databases hosted on Railway. At certain intervals, multiple databases crash at the same time. In some cases, even databases that are not actively being used stop working unexpectedly.

When this happens, all affected services lose database connectivity and my applications become unavailable. The only way I have been able to restore functionality is by redeploying the database service.

This issue has happened several times and last night it occurred again, affecting multiple databases simultaneously and causing downtime for my customers.

From the logs, it appears that the container restarts and MySQL initializes again. However, there is no clear error indicating why the databases stop responding.

Container logs:

2026-02-11T22:17:06.159160Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.

2026-02-11T22:17:06.162497Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.

2026-02-11T22:17:06.237941Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock

2026-02-11T22:17:06.238013Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '9.4.0' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server - GPL.