a month ago
My CashPilot application and MySQL show "EU West — Amsterdam" in the settings. The active application deployment shows "ams," yet getenv('RAILWAY_REPLICA_REGION') returns "iad." I did not create this variable manually.
The application uses mysql.railway.internal:3306. A test run within the application yielded the following results:
DNS: 2.5 ms;
TCP connection directly to the resolved internal IP: 84 ms (consistent across three tests);
New PDO connection: 254 ms;
SELECT 1: approximately 169 ms.
Could you verify the actual service locations and the private network path? This latency compounds across queries, causing several pages to load slowly.
1 Reply
a month ago
Your settings are correct. On the Free plan, a service without a volume isn't guaranteed to run in its selected region: each deploy places it in whichever region has the most available capacity at that moment, which is why your app reports iad (US East) while it shows EU West in settings. Your MySQL service has a volume, so it stays in EU West. That cross-region distance is where the extra latency on your private network connection comes from.
To keep the app in EU West next to your database, move the workspace to Hobby or above and redeploy. After that, every deploy uses the region you selected.
Status changed to Awaiting User Response Railway • about 1 month ago
24 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 • 24 days ago