So is it normal to have my routing through servers in EUROPE from Calgary when I am connecting to my broker which is located in the United States?
Here is my traceroute
Tracing route to cdc1.ibllc.com [126.96.36.199]
over a maximum of 30 hops:
1 * 9 ms 9 ms XXXXXXXXX
2 10 ms 10 ms 11 ms rc3no-be121-1.cg.shawcable.net [188.8.131.52]
3 25 ms 25 ms 26 ms rc2wt-be100.wa.shawcable.net [184.108.40.206]
4 28 ms 28 ms 27 ms rc1wt-be18-1.wa.shawcable.net [220.127.116.11]
5 32 ms 28 ms 28 ms sea-b2-link.telia.net [18.104.22.168]
6 30 ms 27 ms 28 ms level3-ic-335731-sea-b2.c.telia.net [22.214.171.124]
7 * 56 ms 57 ms ae-1-3515.ear2.Chicago2.Level3.net [126.96.36.199]
8 57 ms 57 ms 56 ms INTERACTIVE.ear2.Chicago2.Level3.net [188.8.131.52]
9 56 ms 56 ms 57 ms 184.108.40.206
That isn't going through Europe..
sea is Seattle. Plus each time going across the ocean would add a significant bump in the time (ms) it takes.
That is just passing through Telia in Seattle to get to the Level3 network.
thank you kevinds that is helpful. A few of the geoip sites had the sea site located in France - I also asked because the ping was higher (~20ms) in this location than a previous address that we lived at.
I am happy with Shaw except for this high ping to the broker (~60ms) and to the data feed provider (~80ms).
This is my route.
Tracing route to 220.127.116.11 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms untangle.gateway.com [192.168.1.1]
2 23 ms 11 ms 9 ms 70.76.x.x
3 11 ms 11 ms 8 ms 18.104.22.168
4 24 ms 22 ms 18 ms rc4fs-tge0-14-0-15.mt.shawcable.net [22.214.171.124]
5 28 ms 27 ms 30 ms rc3ec-hge0-17-0-7.il.shawcable.net [126.96.36.199]
6 27 ms 32 ms 36 ms ae-1.a00.chcgil09.us.bb.gin.ntt.net [188.8.131.52]
7 * 29 ms 29 ms Xe-9-1-edge2.nwr1.level3.net [184.108.40.206]
8 * * * Request timed out.
9 38 ms 39 ms 36 ms INTERACTIVE.ear2.Chicago2.Level3.net [220.127.116.11]
10 38 ms 38 ms 34 ms 18.104.22.168
Thank you vanadiel - this is helpful - your route is taking a faster path through Shaw's networks. What is your location?
Can someone from Shaw support weigh in here?
Based on the traceroutes, it is going through a Seattle server. I ran a quick traceroute from our Vancouver office and get about 31 ms when connecting to Seattle. After that, it may be due to a firewall (protection from any DDOS attacks) that seems to slow things down. Therefore, I am getting about 63 ms when it reaches Chicago. Unfortunately, once it leaves the Shaw network, we don't have much control over which route it takes. Generally, it will take the most reliable route possible.
Tony | Community Mod.
Tony | Community Mod.
True, but Shaw has control over which routes it takes when leaving the Shaw network.
For example entering the US in Seattle or Chicago