vince1
April 2, 2025, 7:43am
1
Hi, and thanks for the great platform.
For some reason, both my ISP (RSAWeb) and my mobile data provider (Vodacom) are routing traffic to my instance in jnb via either cdg or fra edge regions, resulting in much higher than expected latency.
$ curl -s -I -H "flyio-debug: doit" https://embark-api.fly.dev | grep flyio-debug
{
"n": "edge-nac-cdg1-0d6d",
"nr": "cdg",
"ra": "165.0.96.198",
"rf": "Verbatim",
"sr": "jnb",
"sdc": "jnb1",
"sid": "d8dd795a125498",
"st": 0,
"nrtt": 0,
"bn": null,
"mhn": "worker-cf-jnb1-7c16",
"mrtt": 166
}
Interestingly it seems some users may be hitting the jnb edge as expected:
However, that would ideally all be going via jnb edge, since the user base right now is definitely all situated in South Africa.
So is there anything I can do about this routing issue, or am I left at the mercy of local ISPs?
can you/users run a mtr/traceroute to your app’s IP and post it here? mtr -bzo "LSD NABVW" embark-api.fly.dev
vince1
April 2, 2025, 10:05am
3
Hi lillian
Thanks for the response.
local-pc (192.168.0.114) -> embark-api.fly.dev (66.241.125.160)
My traceroute [v0.95]
Keys: Help Display mode Restart statistics Order of fields quit
Host Packets Pings
Loss% Snt Drop Last Avg Best StDev Wrst
1. AS??? _gateway (192.168.0.1) 0.0% 69 0 2.2 2.1 0.7 1.8 11.5
2. AS37053 165.0.96.1 (165.0.96.1) 0.0% 69 0 3.4 7.1 2.2 12.1 86.5
3. AS37053 41.71.65.153 (41.71.65.153) 0.0% 69 0 2.4 2.9 2.0 0.6 6.3
4. AS37662 196.250.236.22 (196.250.236.22) 0.0% 69 0 3.1 6.1 1.3 17.3 104.8
5. AS37662 154.66.247.234 (154.66.247.234) 0.0% 68 0 203.4 169.8 143.2 24.1 203.7
6. AS37662 154.66.247.99 (154.66.247.99) 0.0% 68 0 115.2 126.4 114.1 23.8 203.4
7. AS37662 154.66.247.225 (154.66.247.225) 0.0% 68 0 154.3 168.8 143.6 23.0 207.9
8. (waiting for reply)
9. (waiting for reply)
10. AS40509 ip-66-241-125-160.shared.customer.flyio.net (66.241.125.160) 0.0% 68 0 203.1 184.2 157.0 20.5 204.1
our upstream provider seems to have fixed the issue, could you try again now?
vince1
April 2, 2025, 12:58pm
5
Something has definitely changed, but I seem to no longer be able to reach fly.io at all.
curl -s -I -H "flyio-debug: doit" https://embark-api.fly.dev | grep flyio-debug times out.Sign in to Your Account · Fly times out in the browser.
Here’s the current mtr:
vince-pc (192.168.0.114) -> embark-api.fly.dev (66.241.125.160)
Keys: Help Display mode Restart statistics Order of fields quit
Host Packets Pings
Loss% Snt Drop Last Avg Best StDev Wrst
1. AS??? __gateway (192.168.0.1) 0.0% 99 0 2.2 1.3 0.8 0.7 3.8
2. AS37053 165.0.96.1 (165.0.96.1) 1.0% 99 1 18.6 5.1 2.0 4.5 28.6
3. AS37053 41.71.65.153 (41.71.65.153) 0.0% 99 0 5.5 2.7 1.9 0.5 5.5
4. AS37662 196.250.236.22 (196.250.236.22) 0.0% 99 0 2.2 3.7 1.6 7.1 69.5
5. AS37662 154.66.247.234 (154.66.247.234) 0.0% 99 0 146.8 145.7 143.4 6.2 202.9
6. AS37662 154.66.247.99 (154.66.247.99) 0.0% 99 0 114.5 115.3 114.2 2.5 133.9
7. AS37662 154.66.247.225 (154.66.247.225) 0.0% 99 0 145.1 146.5 143.6 7.6 210.5
8. (waiting for reply)
vince1
April 2, 2025, 1:31pm
6
vince-pc (192.168.0.114) -> embark-api.fly.dev (66.241.125.160) My traceroute [v0.95]
Keys: Help Display mode Restart statistics Order of fields quit
Host
1. AS??? _gateway (192.168.0.1) 0.0% 53 0 0.8 0.8 0.7 0.1 1.1
2. AS37053 165.0.96.1 (165.0.96.1) 0.0% 53 0 2.2 5.5 1.9 5.1 24.8
3. AS37053 41.71.65.153 (41.71.65.153) 1.9% 53 1 2.7 2.4 1.9 0.6 4.4
4. AS37662 196.250.236.22 (196.250.236.22) 0.0% 53 0 1.4 2.0 1.4 0.9 5.7
5. AS37662 154.66.247.234 (154.66.247.234) 0.0% 53 0 143.4 144.0 143.2 2.7 162.8
6. AS37662 154.66.247.99 (154.66.247.99) 0.0% 53 0 115.3 114.9 114.0 1.3 121.3
7. AS37662 154.66.247.225 (154.66.247.225) 0.0% 53 0 143.7 144.7 143.7 2.1 152.7
8. (waiting for reply)
9. (waiting for reply)
10. AS40509 ip-66-241-125-160.shared.customer.flyio.net (66.241.125.160) 0.0% 52 0 157.9 157.4 156.8 1.0 160.8
Okay going through all the way again, but still looks like an international hop.
vince1
April 2, 2025, 6:54pm
7
Host Packets Pings
Loss% Snt Drop Last Avg Best StDev Wrst
1. AS??? _gateway (192.168.0.1) 0.0% 62 0 2.2 1.9 0.8 0.6 3.0
2. AS37053 165.0.96.1 (165.0.96.1) 0.0% 62 0 17.0 9.8 1.9 17.8 104.7
3. AS37053 41.71.65.153 (41.71.65.153) 0.0% 62 0 2.9 2.7 2.0 0.4 4.0
4. AS5713 wdcnw-os-cer-1-etht-177-88880130.osnet.co.za (196.25.10.133) 0.0% 61 0 2.3 4.2 0.6 2.2 49.3
5. AS??? pccw.ixp.capetown (196.60.70.25) 0.0% 61 0 253.4 253.9 251.3 6.9 307.0
6. AS3491 Hu0-0-0-20.br03.jnb01.as3491.net (63.222.48.142) 1.6% 61 1 254.6 255.0 252.7 7.5 308.9
7. AS3491 63-222-113-151.static.as3491.net (63.222.113.151) 0.0% 61 0 19.8 24.8 18.9 20.3 127.7
8. AS40509 ip-66-241-125-160.shared.customer.fly.io (66.241.125.160) 0.0% 61 0 18.7 23.0 18.3 17.1 109.10
Above is latest trace, and by the looks of the flyio-debug headers, it confirms the jnb edge is now being used.
$ curl -s -I -H "flyio-debug: doit" https://embark-api.fly.dev | grep flyio-debug
{
"n": "edge-cf-jnb1-5772",
"nr": "jnb",
"ra": "165.0.96.198",
"rf": "Verbatim",
"sr": "jnb",
"sdc": "jnb1",
"sid": "d8dd795a125498",
"st": 0,
"nrtt": 0,
"bn": "worker-cf-jnb1-7c16",
"mhn": null,
"mrtt": null
}
Thanks for the quick help!
system
April 9, 2025, 6:54pm
8
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
