Support Board
Date/Time: Sun, 24 Nov 2024 05:45:26 +0000
Post From: Problems with Denali Data Feed
| [2024-05-28 21:00:17] |
| nosast - Posts: 312 |
|
@Sierra_Chart Engineering I just read the thread "Sierra Chart Internet Connectivity Related Issues" and as it's locked I will respond here. As you already know I'm really looking forward do be connected to the new DC or at least without Cogent as peering partner in the trace. As I have a network statistics tool running during RTH I get notified about latency issues like paket loss and jitter immediately and can say with 99% certainty that Cogent is causing all these issues for guys connecting from overseas (I'm located in Europe). Teton order routing on the other hand is peering via Zayo and is rock solid so I would have loved to Zayo as the new ISP for the Michigan DC. But the solution you are implementing right now looks good if 123.net is really peering to Zayo, Lumen, NTT, AT&T or any of the other big Tier1 carrier. Please let me know if I could be of any help. If you send over an IP I can run continues monitoring tests for a first check (at least for connections from Europe). For the time being I added 123.net into the monitoring (the IP behind this URL is out of their network AS12129) and therefore should be a good first indication. The only thing to think about is that 123.net accoriding to peeringdb.com only has a few locations all in Detroit area with no connection to bigger peering/exchange points. https://www.peeringdb.com/org/10627 But this may also be a good thing as e.g. CH1 Equinix is very crowded and has quite some realtime latency issues across all carriers which should not be the case in Detroit. If you think about it that get's pretty obvious how much data in realtime gets distributed out of the worlds central futures exchanges out of Chicago area. Current route to 123.net over 9 hops (looks good to me) 3 1 0 11.04 11.04 11.04 m-ef2-i.M.DE.NET.DTAG.DE [217.0.194.22] 4 1 0 10.84 10.84 10.84 m-ef2-i.M.DE.NET.DTAG.DE [217.0.194.22] 5 1 0 13.21 13.21 13.21 80.150.168.185 [80.150.168.185] 6 1 0 105.46 105.46 105.46 ae5.cr1-det3.ip4.gtt.net [89.149.143.133] 7 1 0 117.70 117.70 117.70 ip4.gtt.net [66.171.226.42] 8 1 0 112.71 112.71 112.71 67.214.125.193 [67.214.125.193] 9 1 0 112.52 112.52 112.52 123.net [216.109.194.6] Compared to the current Cogent route over 16 hops 3 11 0 9.32 10.02 9.64 f-ed12-i.F.DE.NET.DTAG.DE [217.0.192.202] 4 11 0 8.54 72.75 19.53 f-ed12-i.F.DE.NET.DTAG.DE [217.0.192.202] 5 11 0 8.44 9.64 8.95 80.150.170.131 [80.150.170.131] 6 11 18 8.72 13.68 9.50 be3187.ccr42.fra03.atlas.cogentco.com [130.117.1.118] 7 10 0 14.28 15.31 14.90 be2814.ccr42.ams03.atlas.cogentco.com [130.117.0.141] 8 10 0 110.18 111.02 110.64 be12488.ccr42.lon13.atlas.cogentco.com [130.117.51.41] 9 10 0 109.05 111.16 109.75 be3488.ccr52.lhr01.atlas.cogentco.com [154.54.60.14] 10 10 0 109.90 111.12 110.45 be4283.ccr32.bos01.atlas.cogentco.com [154.54.47.145] 11 10 0 114.81 115.55 115.30 be3600.ccr22.alb02.atlas.cogentco.com [154.54.0.221] 12 10 0 110.00 111.04 110.50 be2879.ccr22.cle04.atlas.cogentco.com [154.54.29.173] 13 10 0 108.98 110.12 109.56 be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129] 14 10 0 114.88 115.45 115.15 be2766.ccr41.ord03.atlas.cogentco.com [154.54.46.178] 15 10 0 111.27 111.79 111.48 be2051.agr61.ord03.atlas.cogentco.com [154.54.84.50] 16 10 0 108.68 109.65 109.16 38.103.112.197 [38.103.112.197] Attached is also a latency stat from the monitoring of 123.net. Jitter is very good/minimal at the moment. Date Time Of Last Edit: 2024-05-28 21:08:21
|
 SNAG_ 2024-05-28 - 22-59-12.png / V - Attached On 2024-05-28 20:59:35 UTC - Size: 110.37 KB - 54 views |