All six of your services were redeployed within the same one-minute window (around 08:24 UTC today), which is consistent with a Railway-initiated migration. On the Hobby plan, we occasionally move services to different hosts for workload optimization, security patches, or infrastructure upgrades - this is documented in our deployment reference. These migrations are automatic and do not require manual redeployment on your part, as Railway handles the redeployment. If your services are not coming back up after a migration, that would indicate an application-level issue such as a crash on startup.