Hey there! We've found the following might help you get unblocked faster:

• 🧵 Updating Flowise

• 🧵 My Instance is slow, I just updated to the Hobby plan but it's still slow

• 🧵 DEPLOYEMENT CRASH

If you find the answer from one of these, please let us know by solving the thread!

Can you screenshot the region section, just to make sure, before I escalate this? I can confirm on my machine it is hitting Singapore.

Here is the screen shot:

I added an static IP address in Europe bit it isnt deployed yet. I believe the re-routing to Singapore is causing latency and possible GDPR issues, so please can you resolve as soon as possible.

Hello,

What geolocation are you running the ping from?

Hi I'm running the ping from the UK from this IP: 82.34.182.250

Can you run a traceroute to your Railway service domain, please?

chriskey@Chriss-MacBook-Pro ~ % traceroute -I agents.cxcortex.ai

traceroute to o9lbg576.up.railway.app (66.33.22.232), 64 hops max, 48 byte packets

 1  192.168.0.1 (192.168.0.1)  2.749 ms  2.281 ms  1.686 ms

 2  * * *

 3  80.255.197.40 (80.255.197.40)  17.480 ms  11.458 ms  15.151 ms

 4  * * *

 5  * * *

 6  * * *

 7  host-62-254-42.162.not-set-yet.virginmedia.net (62.254.42.162)  24.527 ms  36.279 ms  26.037 ms

 8  * adm-b3-link.ip.twelve99.net (62.115.187.126)  21.577 ms  23.905 ms

 9  adm-bb2-link.ip.twelve99.net (62.115.138.170)  24.185 ms  24.603 ms  26.192 ms

10  adm-b12-link.ip.twelve99.net (62.115.137.191)  28.703 ms  23.496 ms  22.702 ms

11  railwaycorp-ic-390073.ip.twelve99-cust.net (62.115.196.223)  22.147 ms  24.894 ms  21.426 ms

12  66.33.22.232 (66.33.22.232)  23.441 ms  23.949 ms  23.200 ms

chriskey@Chriss-MacBook-Pro ~ % 

Attached DNS setting in Godaddy.

Can you clarify what shows as Singapore when you're pinging? We use an anycast IP for all services, so the geolocation of the resulting IP doesn't matter. Based on your traceroute, it looks like that's behaving as expected

Static IPs do not matter here as they're only for outbound requests.

I pinged the domain and got the Singapore IP address.

So the concern is whether traffic to/from the server was always following this route which it seems to be. I would expect anycast to establish a shorter route than the 14,000 miles to Singapore and back? So it looks like our data is transiting via Singapore and possibly is at rest there, could you clarify and how do we resolve this please?

Your traffic isn't transiting to Singapore according to the traceroute you provided. The latency would be much higher if it were, and you would be seeing a different trace that bounces to a different ISP.

With anycast, multiple servers share the same IP address. When trying to send data to an anycast IP, the router will route the data to the nearest healthy server based on network latency, routing configuration, or geographical proximity. We have servers announcing the same IP across different regions.

The service you're using to look up the IP may be resolving it from Singapore, hence it's getting a response from our Singapore node.

To further clarify... The traceroute confirms you're hitting a European node, not Singapore. According to your traceroute:

• Your traffic is going through Virgin Media -> Telia/Twelve99 (a European backbone), and the adm prefix means Amsterdam -> Railway's network. There is no other transit provider in this path.

• The latency is another hint at this: a round-trip time of ~23ms is consistent with UK -> Amsterdam (where Railway's EU datacentres are located). Singapore <-> UK would likely be in the range of 150~300ms.

• The service you're using to check the geolocation likely runs their lookup from infrastructure near or around Singapore where it's getting routed to our Singapore node. If you look at other lookup services such as https://ipinfo.io/66.33.22.232, it shows as US because they're either looking it up near or around the US, or using our registration data.

Ok thanks for the clarity on that. I'll close the ticket.