14 days ago
Hi, I have two services:
Kong Gateway — Public network
WebSocket Service — Private network (users access this through Kong)
Both services are deployed across multiple regions, with one replica per region.
When a request comes in, Kong correctly routes the user to the Singapore gateway.
However, when Kong forwards the request to the WebSocket service, it randomly picks a region (EU, US, etc.).
I expect Kong to forward the request to the WebSocket instance in the same region (Singapore), but that’s not happening.
5 Replies
14 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Awaiting Conductor Response brody • 14 days ago
14 days ago
Hey, according to the Railway documentation, the multi-region routing is only for public networking. I assume that the private networking's routing is unspecified for multi-region, in which it falls back to the base case of distributing traffic randomly as if the target was a single region service with multiple replicas. I'll ask internally to see if this is the intended behavior.
Status changed to Awaiting User Response Railway • 14 days ago
uxuz
Hey, according to the Railway documentation, the multi-region routing is only for public networking. I assume that the private networking's routing is unspecified for multi-region, in which it falls back to the base case of distributing traffic randomly as if the target was a single region service with multiple replicas. I'll ask internally to see if this is the intended behavior.
14 days ago
Yes, thank you. Please check with the Railway team. It’s surprising that Railway can’t route traffic within the same region. With multiple services, this becomes problematic, public requests are routed correctly, but internal traffic is still slow, which makes the setup much less useful.
I found the documentation about the private network, but it doesn’t mention this limitation.
Status changed to Awaiting Conductor Response Railway • 14 days ago
tiendvlp
Yes, thank you. Please check with the Railway team. It’s surprising that Railway can’t route traffic within the same region. With multiple services, this becomes problematic, public requests are routed correctly, but internal traffic is still slow, which makes the setup much less useful.I found the documentation about the private network, but it doesn’t mention this limitation.https://docs.railway.com/reference/private-networking
14 days ago
Hey, unfortunately, there is no region awareness when using private networking. I will change the topic of this thread to a feedback for region aware private networking for this feature to be considered.
Status changed to Awaiting User Response Railway • 14 days ago
Status changed to Solved tiendvlp • 14 days ago
uxuz
Hey, unfortunately, there is no region awareness when using private networking. I will change the topic of this thread to a feedback for region aware private networking for this feature to be considered.
14 days ago
Yes, I think this is a significant downside for anyone using a microservices architecture. For now, I will try to keep all of my services in the Singapore region only. But I really hope the team will add this feature soon. Thank you for your support.
Status changed to Awaiting Conductor Response Railway • 14 days ago
Status changed to Solved tiendvlp • 14 days ago

