a month ago
I'm experiencing two related networking issues affecting my production environment:
1. Edge routing to wrong region
My services are deployed in us-east, and my users are located in Brazil. However, incoming requests are being routed through the eu-west edge instead of a US.
2. TLS handshake errors
Some of my clients are experiencing HTTP connection failures with TLS handshake errors. I suspect this may be related to the incorrect edge routing above, possibly due to certificate mismatch or proxy misconfiguration when traffic is being routed through an unintended edge region (just assuming).
28 Replies
a month ago
Based on this report https://discord.com/channels/713503345364697088/1512494819434561606
I removed the DNS and added it again after 30 minutes, now it's working again.
a month ago
The second one is solved, the first one is an ongoing issue.
a month ago
Hi @Henrique Antonio, please could you go to https://railway.com/.railway/cdn-trace and let me know what the pop field is equal to?
a month ago
pop=ams1
a month ago
Could you perform an MTR/traceroute to 69.46.46.46 if possible?
a month ago
Start: 2026-06-06T18:21:37-0300
HOST: me Loss% Snt Last Avg Best Wrst StDev
1.|-- [gateway-1] 0.0% 10 2.0 1.7 1.3 2.3 0.3
2.|-- [gateway-2] 0.0% 10 2.6 3.1 1.9 10.4 2.6
3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
5.|-- 172.200.0.138 0.0% 10 3.7 3.3 2.5 3.9 0.5
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 172.200.0.245 0.0% 10 6.0 6.9 4.5 16.4 3.4
8.|-- 172.200.0.246 0.0% 10 6.3 23.5 4.3 65.6 21.8
9.|-- 172.200.0.249 0.0% 10 22.3 21.7 17.3 40.1 6.7
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 186.192.136.48 0.0% 10 19.9 19.8 18.6 20.3 0.5
12.|-- 177.190.108.134 0.0% 10 18.9 19.4 18.5 20.3 0.6
13.|-- 177.190.108.187 0.0% 10 126.0 125.2 124.4 126.0 0.6
14.|-- speed-ix.cdn77.com 0.0% 10 208.6 208.8 207.2 215.8 2.5
15.|-- vl232.ams-eq6-core-2.cdn7 0.0% 10 202.3 203.5 202.0 207.9 1.7
16.|-- vl221.ams-eq6-dist-1.cdn7 0.0% 10 201.7 202.5 201.0 209.2 2.4
17.|-- 69.46.46.46 0.0% 10 200.4 201.3 199.9 208.9 2.7a month ago
Could you check https://railway.com/.railway/cdn-trace now?
a month ago
v=hikari:0.1.2:1305a1583dc517b7e2603638b5710b21
r=production-hikari-dpams-1
pop=ams1
node=kxr8
ts=178078125969a month ago
Hmm ok, if you perform the traceroute again do you still see speed-ix on hop 14?
a month ago
Yep
a month ago
Could you check again please?
a month ago
Same asm1 and hop 14 speed-ix.cdn77.com
a month ago
Any update?
a month ago
Hello, please could you check again? 🙏
a month ago
HOST: me Loss% Snt Last Avg Best Wrst StDev
1.|-- [gateway-1] 0.0% 10 2.6 2.3 1.3 3.6 0.7
2.|-- [gateway-2] 0.0% 10 4.0 4.1 1.9 13.4 3.4
3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
5.|-- 172.200.0.138 0.0% 10 3.8 4.8 2.7 9.3 1.9
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 172.200.0.245 0.0% 10 10.3 9.8 5.8 23.2 5.3
8.|-- 8.61.86.187.static.opcaot 0.0% 10 4.9 5.2 3.7 6.1 0.7
9.|-- ae150.1590.edge8.gru1.as7 0.0% 10 17.2 17.4 16.0 19.8 1.2
10.|-- ae1255.0.edge2.jfk1.as719 0.0% 10 125.6 127.2 124.1 134.8 3.0
11.|-- ae1144.0.edge1.lon1.as719 0.0% 10 198.1 197.4 193.4 204.9 3.8
12.|-- ae449.0.edge1.fra1.as7195 0.0% 10 208.3 209.5 205.4 215.3 3.3
13.|-- ae10-1.fra30.core-backbon 0.0% 10 207.9 207.9 206.0 216.3 3.0
14.|-- ae5-2074.ams10.core-backb 0.0% 10 211.5 211.8 210.7 215.0 1.3
15.|-- coreb-ams.cdn77.com 0.0% 10 212.0 210.1 208.2 212.0 1.2
16.|-- vl221.ams-eq6-dist-1.cdn7 0.0% 10 208.0 210.5 207.4 221.6 4.4
17.|-- 69.46.46.46 0.0% 10 207.9 207.5 205.4 210.5 1.5```a month ago
HI! 🙂
a month ago
ughh why does a brazilian isp peer in amsterdam lol
a month ago
let me try something else
a month ago
ok
a month ago
I've done some research, but I'm not deep in this area. My best guess is that Brazilian traffic ends up in Amsterdam because that route is cheaper for the ISPs, while going through US-East has a cost attached to it
a month ago
The current edges that my service are receiving are us-west2 and us-east4-eqdc4a
a month ago
Start: 2026-06-08T15:14:27-0300
HOST: me Loss% Snt Last Avg Best Wrst StDev
1.|-- [gateway-1] 0.0% 10 1.9 1.9 1.1 2.5 0.4
2.|-- [gateway-2] 0.0% 10 2.4 2.0 1.4 2.5 0.4
3.|-- 100.127.255.255 0.0% 10 5.6 5.8 3.9 9.5 2.1
4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
5.|-- 172.200.0.138 0.0% 10 3.9 3.4 2.1 4.5 0.8
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 172.200.0.245 0.0% 10 6.9 6.7 4.3 12.4 2.8
8.|-- 8.61.86.187.static.opcaot 0.0% 10 4.8 4.7 3.8 5.7 0.6
9.|-- ae150.1590.edge8.gru1.as7 0.0% 10 16.6 16.2 15.5 16.8 0.4
10.|-- ae1255.0.edge2.jfk1.as719 0.0% 10 125.9 125.2 124.3 127.7 1.0
11.|-- ae1144.0.edge1.lon1.as719 0.0% 10 194.5 195.9 193.2 204.0 4.0
12.|-- ae449.0.edge1.fra1.as7195 0.0% 10 205.6 207.8 204.8 215.7 4.2
13.|-- ae10-1.fra30.core-backbon 0.0% 10 206.0 206.7 204.8 211.4 1.8
14.|-- ae5-2089.ber10.core-backb 0.0% 10 212.7 212.8 211.9 216.6 1.4
15.|-- coreb-ber.cdn77.com 0.0% 10 218.0 217.0 216.1 218.0 0.6
16.|-- vl221.ber-ipb-dist-2.cdn7 0.0% 10 215.8 215.4 214.3 217.4 1.0
17.|-- 69.46.46.46 0.0% 10 216.7 216.5 215.8 217.8 0.6a month ago
The pop is pop=ber1
a month ago
It’s likely not cheaper for them, but their routing is just not optimized for reachability to Railway. The culprit is EdgeUno and I’m finding it very hard to engineer traffic from that network :(
a month ago
EdgeUno is a LATAM transit network, but for some reason they’ve decided to upstream and peer with European transit networks which makes our network seem much closer in Europe than the US.
a month ago
We actually do have a Sao Paolo POP coming online soon, so once that’s up you should see resolution here - and much faster connection times
a month ago
That's great
a month ago
The service edge are on us-west2 and us-east4-eqdc4a because probabilly my DNS are proxied by Cloudflare, i'm correct?