.

Hello passatgt,

i think the latency gap is normal , on hostinger your app and db run on the same machine so network cost is zero, on railway they're separate services so every query has a network round trip

two things to check, first hat is your db_host set to? if it's a public hostname you're routing every query over the public internet. switch it to the private .railway.internal hostname from your mysql service settings

and second are both your app and mysql service in the same region? if not, railway docs say you get 50-150ms added per query by design

so can you share what your db_host is and which region each service is deployed to?

I think the issue may be in how the MySQL database is being accessed on railway. If you are accessing it using the internal link, it should be much faster, but through DATABASE_PUBLIC_URL, it will bring about more cost and less speed. So try connecting using the internal url and ssh directly into the instance using railway command line. Also put the services in the same project to consume the DB internally.

(The application already uses private networking. You can check this through its preconfigured variables when deploying the template.)

ok then i think it's the region mismatch, @passatgt are both your app and mysql service deployed in the same region? you can check this in each service's settings tab

By default, services will be deployed in the user's preferred region (under account settings), but doesn't hurt to check.

Yes, using private networking, same region, so thats not the issue.