a year ago
I changed the region to Singapore on my service, but it stays on the US. Recently changed to the Netherlands but it is still not Singapore
5 Replies
a year ago
Do you get any error messages ?
No, I don't have any errors. Here's my URL - https://rms2.up.railway.app/ And this is my config ```{ "$schema": "https://railway.app/railway.schema.json", "build": { "builder": "NIXPACKS" }, "deploy": { "region": "asia-southeast1", "numReplicas": 1, "sleepApplication": false, "restartPolicyType": "ON_FAILURE", "restartPolicyMaxRetries": 10 } }```
Attachments
a year ago
When you ping/lookup a service hosted on Railway, it goes through our edge network that will pick the location nearest to you before routing it to the location where your service is deployed in.
If you're connecting from US, you'll see the US IP (& we route that traffic to the instance in Singapore). If you're connecting from Singapore, you'll see the Singapore IP.
a year ago
When you ping/lookup a service hosted on Railway, it goes through our edge network that will pick the location nearest to you before routing it to the location where your service is deployed in.
If you're connecting from US, you'll see the US IP (& we route that traffic to the instance in Singapore). If you're connecting from Singapore, you'll see the Singapore IP.
What if I request for example from Europe or Central Asia?
a year ago
We'll pick the shortest-path to the region of your instance for your users, depending on our edge network's availability in those regions.
In all cases, traffic will hit your instance in the region you choose - they're just routed differently. So, deploying an instance in Singapore would be fastest if you were connecting from SE Asia, but if you make a request to that instance from the US, you'll see the IP address of our edge network that routes it to Singapore.
22 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 • 22 days ago