Support Board
Date/Time: Sun, 24 Nov 2024 03:53:43 +0000
Problems with Denali Data Feed
View Count: 3261
| [2024-06-06 21:04:10] |
| nosast - Posts: 312 |
|
Time zone is Central European so 1:37 pm Chicago time. I totally understand that the path the pakets use is out of your control and dependet on the connectivity of the datacenter and the BGP peering between the Tier1 carriers. I also know that the path back and from could and often will be totally different. Also some days Cogent is fine, while GTT is having latency issues and vice versa. Tough to resolve for sure so the best is to have a few options like we have right now to connect do different DCs/peerings. Regarding my home carrier. I have two and Deutsche Telekom still has the best private peerings crossing the Atlantic. In a few months I get a fibre connecting from a smaller carrier using mostly public peerings instead of private like Deutsche Telekom hoping this will have an positive effect. Again: I'm not blaming you guys. Sierra is the best by far! Just want to inform and know if ds32 is ready for live connections. |
| [2024-06-07 11:00:34] |
| Rui S - Posts: 190 |
|
Also some days Cogent is fine, while GTT is having latency issues and vice versa
This is absolutely true! I'm in Portugal and last week Cogent connection and latency was terrific (very stable and very low latency) whereas this week it has been terrible and sometimes simply unusable. Fortunately, SC has already redundancy to Cogent, which I have been able to use with no problems, despite its higher latency. For Sierra Charts Engineering: My standard for comparison has always been another data provider connection routing - very stable and very low latency, the lowest from Chicago to Europe so far. Would it be worth for you to check and try this ISP? (screenshot attached) I truly believe that could definitely resolve these nasty issue for all of us! Again: I'm not blaming you guys. Sierra is the best by far!
I make the above my words too! Sierra forever!! Date Time Of Last Edit: 2024-06-07 11:02:11
|
001.jpg| [2024-06-07 11:11:59] |
| nosast - Posts: 312 |
|
@Rul S: the trace you posted shows Hurricane Eletric (he) as the main peering partner for your Rithmic connection. I think Hurricane is also mentioned as an ISP when the final switch to Michigan has been done. |
| [2024-06-07 11:27:49] |
| Rui S - Posts: 190 |
|
@Rul S:
the trace you posted shows Hurricane Eletric (he) as the main peering partner for your Rithmic connection. I think Hurricane is also mentioned as an ISP when the final switch to Michigan has been done @nosast Thank you for your information. I didn't write the name of the data provider as it didn't seem proper. Hopefully you are correct and Sierra will be using that ISP too, that would be great news for us all. That ISP has been by far the one that is better, both in stability and latency. Every time I have connection problems with the other ISPs, this one is always good. |
| [2024-06-10 19:40:03] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Hurricane Electric is certainly one of the ISPs that can be used but this is based upon the BGP routing tables, as we are told.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-06-10 20:45:22] |
| Rui S - Posts: 190 |
|
Hurricane Electric is certainly one of the ISPs that can be used but this is based upon the BGP routing tables, as we are told.
I don't know what "BGP routing tables" means, but if this ISP Hurricane Electric is the same that Rithmic is using for Europe, I can assure you that the service is very stable and the one with less latency by far. I've been monitoring it every single day for a long time now, along with Interactive Brokers data feed and also Denali. A ISP service with such quality would certainly be an important improvement to the already high quality standards of Sierra Charts / Denali. |
| [2024-06-15 20:21:49] |
| Sierra_Chart Engineering - Posts: 17154 |
|
We do not know a whole lot about Hurricane Electric, but it is in the low price category along with Cogent and GTT. We do have access to it, but we cannot force the routing through it. Depends upon the routing tables. Nosast and anyone else, Can you run a trace route to these following IPs: 12.55.168.193 (AT&T) 4.69.148.45 (Lumen) 184.104.192.202 (Hurricane electric) Provide results here. We will look at adding Hurricane Electric, but we have to figure out how to handle routing when there are multiple ISPs. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-06-15 21:52:03
|
| [2024-06-16 15:53:28] |
| BenjFlame - Posts: 324 |
|
From France: Tracing route to 12.55.168.193 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms **.home ** 2 2 ms 1 ms 3 ms 80.***** 3 2 ms 2 ms 2 ms ae108-0.ncidf203.rbci.orange.net [193.249.212.102] 4 2 ms 2 ms 2 ms ae41-0.niidf201.rbci.orange.net [193.252.98.161] 5 2 ms 2 ms 2 ms ae40-0.niidf202.rbci.orange.net [81.253.129.186] 6 * 2 ms 2 ms 193.252.137.74 7 78 ms 78 ms 78 ms 193.251.133.137 8 * * * Request timed out. 9 * * * Request timed out. ......... Then the request hops timeout continues indefinitely. I think their network don't allow such requests. ================= Tracing route to ae2.3601.ear1.Washington12.level3.net [4.69.148.45] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms *.home [192.*] 2 1 ms 1 ms 1 ms 80.* 3 1 ms 1 ms 2 ms ae108-0.ncidf203.rbci.orange.net [193.249.212.102] 4 2 ms 7 ms 4 ms ae41-0.niidf201.rbci.orange.net [193.252.98.161] 5 2 ms 3 ms 2 ms ae40-0.niidf202.rbci.orange.net [81.253.129.186] 6 19 ms 2 ms 3 ms 193.252.137.74 7 8 ms 5 ms 20 ms ae-a5.edge7.Paris1.Level3.net [4.68.127.233] 8 5 ms 6 ms 13 ms ae20.3211.ebr2.par1.neo.colt.net [171.75.9.204] 9 80 ms 80 ms 79 ms ae40.40.ebr4.wdc1.level3.net [171.75.16.5] 10 88 ms 80 ms 80 ms ae15.15.ebr2.Washington12.level3.net [4.69.133.198] 11 80 ms 80 ms 79 ms ae2.3601.ear1.Washington12.level3.net [4.69.148.45] Only 11 hops from France to lumen. This is little for transatlantic connexion. Very nice. ============================ Tracing route to 100ge0-36.core1.cle1.he.net [184.104.192.202] over a maximum of 30 hops: 1 6 ms <1 ms <1 ms *.home [192.*1] 2 1 ms 1 ms 1 ms 80.* 3 2 ms 1 ms 1 ms ae108-0.ncidf203.rbci.orange.net [193.249.212.102] 4 1 ms 1 ms 1 ms ae41-0.niidf201.rbci.orange.net [193.252.98.161] 5 2 ms 2 ms 2 ms ae40-0.niidf202.rbci.orange.net [81.253.129.186] 6 2 ms 2 ms 1 ms 193.252.137.74 7 9 ms 9 ms 9 ms bundle-ether304.lontr5.london.opentransit.net [193.251.241.157] 8 * * * Request timed out. 9 12 ms * * 100ge0-59.core2.lon5.he.net [184.104.198.246] 10 * * * Request timed out. 11 * * 74 ms port-channel8.core2.bos1.he.net [184.104.199.77] 12 * 78 ms 78 ms port-channel8.core2.nyc4.he.net [72.52.92.166] 13 * * * Request timed out. 14 80 ms 80 ms 79 ms 100ge0-36.core2.phl1.he.net [184.105.222.2] 15 87 ms 87 ms 88 ms 100ge0-36.core1.pit1.he.net [184.104.194.197] 16 93 ms 90 ms 90 ms 100ge0-36.core1.cle1.he.net [184.104.192.202] ================================ Tracing route to ds32.sierracharts.com [67.214.125.3] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms *.home [192.*] 2 1 ms 1 ms 1 ms 80.* 3 1 ms 2 ms 1 ms ae108-0.ncidf203.rbci.orange.net [193.249.212.102] 4 1 ms 1 ms 1 ms ae41-0.niidf201.rbci.orange.net [193.252.98.161] 5 * * * Request timed out. 6 * * * Request timed out. 7 3 ms 2 ms 3 ms be3626.ccr42.par01.atlas.cogentco.com [130.117.1.45] 8 78 ms 79 ms 78 ms be3628.ccr42.jfk02.atlas.cogentco.com [154.54.27.169] 9 91 ms 90 ms 91 ms 154.54.162.169 10 93 ms 92 ms 93 ms be3745.rcr51.tol01.atlas.cogentco.com [154.54.30.130] 11 94 ms 94 ms 94 ms be2123.rcr21.dtw04.atlas.cogentco.com [154.54.82.138] 12 91 ms 91 ms 90 ms gi0-0-0-18.204.nr11.b015471-1.dtw04.atlas.cogentco.com [38.122.60.13] 13 88 ms 88 ms 88 ms 67.214.125.193 14 87 ms 88 ms 88 ms 67.214.125.3 Date Time Of Last Edit: 2024-06-16 15:54:04
|
| [2024-06-16 16:38:00] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Some comments on this. Some apparent observations: 7 8 ms 5 ms 20 ms ae-a5.edge7.Paris1.Level3.net [4.68.127.233]
Level3 is lumen. Notice how they pass it off to colt.net crossing the Atlantic. Lumen is not handling this across their own fiber over the Atlantic.8 5 ms 6 ms 13 ms ae20.3211.ebr2.par1.neo.colt.net [171.75.9.204] 9 80 ms 80 ms 79 ms ae40.40.ebr4.wdc1.level3.net [171.75.16.5] Looks like the same thing with Hurricane Electric but we do not know who is in the middle: 9 12 ms * * 100ge0-59.core2.lon5.he.net [184.104.198.246]
10 * * * Request timed out. 11 * * 74 ms port-channel8.core2.bos1.he.net [184.104.199.77] Hurricane Electric is also sending the data up to London, and then over to Boston. Rather than from Paris to the East Coast of the US. Also with Lumen, the closest switch IP we were able to determine, was one in Washington DC. So the latency you see with Lumen, will always look less than actual when going to Michigan. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-06-16 16:38:18
|
| [2024-06-16 17:03:15] |
| BenjFlame - Posts: 324 |
|
That was from a friend in France, from another ISP than mine. This was run on 2, June. Seems to be clean route with Zayo handling everything. But his ping to ds32 is about 10ms slower than mine. |
| [2024-06-16 18:48:58] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Zayo is one of the peers with the Internet from the 123.net data center that we use in Michigan. Your friends ISP is routing data over Zayo. Your ISP is routing it over Cogent. See if you can change to a different ISP if Cogent is giving you trouble but Cogent is not necessarily bad in this case. This is a trace, to DS32 from one of our servers in Germany. As you can see it also takes Zayo route: Tracing route to ds32.Sierracharts.com [67.214.125.3] over a maximum of 30 hops: 3 4 ms 4 ms 4 ms core1.fra.hetzner.com [213.239.224.70] 4 5 ms 7 ms 4 ms as6461.frankfurt.megaport.com [62.69.146.139] 5 105 ms 104 ms 104 ms ae1.cs1.fra9.de.eth.zayo.com [64.125.29.64] 6 * * * Request timed out. 7 108 ms * 107 ms ae2.cs1.ams17.nl.eth.zayo.com [64.125.29.59] 8 * * * Request timed out. 9 104 ms * * ae10.cs1.lhr15.uk.eth.zayo.com [64.125.29.17] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 104 ms 104 ms 112 ms ae10.mpr2.dtw3.us.zip.zayo.com [64.125.24.225] 14 105 ms 105 ms 105 ms 64.124.32.66.IDIA-385104-ZYO.zip.zayo.com [64.124.32.66] 15 104 ms 104 ms 104 ms 67.214.125.193 16 104 ms 104 ms 104 ms 67.214.125.3 Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-06-16 18:54:44
|
| [2024-06-16 19:02:22] |
| BenjFlame - Posts: 324 |
|
Well, I had problems with cogent earlier. Now it seems ok. Actually, my ping with cogent is better than his with Zayo. Around 10ms which is not negligible for transatlantic connexion. |
| [2024-06-16 19:26:34] |
| VLiviu - Posts: 223 |
|
How is it? C:\Users\xxx>tracert ds32.sierracharts.com Tracing route to ds32.sierracharts.com [67.214.125.3] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 192.168.68.1 2 4 ms 2 ms 3 ms 192.168.100.1 3 5 ms 4 ms 4 ms 10.0.0.1 4 5 ms 4 ms 5 ms 10.30.0.193 5 11 ms 17 ms 4 ms 10.220.185.192 6 47 ms 46 ms 47 ms 10.220.187.209 7 48 ms 47 ms 46 ms 195.66.225.227 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 135 ms 135 ms 135 ms ae10.mpr2.dtw3.us.zip.zayo.com [64.125.24.225] 12 134 ms 134 ms 134 ms 64.124.32.66.IDIA-385104-ZYO.zip.zayo.com [64.124.32.66] 13 133 ms 133 ms 133 ms 67.214.125.193 14 133 ms 132 ms 132 ms 67.214.125.3 Trace complete. |
| [2024-06-16 20:39:38] |
| Sierra_Chart Engineering - Posts: 17154 |
|
It seems fine, but the ultimate test is just actually seeing if there any issues when the market is most active.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-06-16 23:24:39] |
| nosast - Posts: 312 |
|
@Sierra_Chart Engineering here are 3 traces from Germany (Deutsche Telekom) Target Name: 12.55.168.193 IP: 12.55.168.193 Date/Time: 17.06.2024 01:18:47 - 17.06.2024 01:28:47 Hop Sent PL% Min Max Avg Host Name / [IP] 1 2 0 0.75 0.87 0.81 fritz.box [192.168.1.1] 2 2 0 4.37 4.59 4.48 p3e9bf597.dip0.t-ipconnect.de [62.155.245.151] 3 2 0 103.75 103.84 103.79 was-sa2-i.WAS.US.NET.DTAG.DE [62.154.5.106] 4 1 100 0 0 0 12.55.168.193 [12.55.168.193] Target Name: ae2.3601.ear1.Washington12.level3.net IP: 4.69.148.45 Date/Time: 17.06.2024 01:12:32 - 17.06.2024 01:22:32 Hop Sent PL% Min Max Avg Host Name / [IP] 1 2 0 0.86 0.88 0.87 fritz.box [192.168.1.1] 2 2 0 10.76 60.01 35.39 p3e9bf597.dip0.t-ipconnect.de [62.155.245.xxx] 3 2 0 9.46 19.39 14.43 f-eh1-i.F.DE.NET.DTAG.DE [217.5.116.254] 4 1 100 0 0 0 [-] 5 2 0 8.63 13.63 11.13 ae1.3116.ebr1.frf1.neo.colt.net [171.75.9.152] 6 2 0 9.12 11.45 10.29 ae3.3.ebr3.frf1.neo.colt.net [171.75.0.1] 7 2 0 8.94 9.46 9.20 ae54.54.ebr2.frf18.neo.colt.net [171.75.0.88] 8 2 0 8.74 9.61 9.17 ae1.100.ebr1.frf18.neo.colt.net [171.75.0.64] 9 2 0 20.75 20.76 20.76 ae49.49.ebr4.par1.neo.colt.net [171.75.0.30] 10 2 0 20.91 21.05 20.98 ae1.100.ebr3.par1.neo.colt.net [171.75.0.112] 11 2 0 101.35 101.46 101.41 ae50.50.ebr4.wdc111.level3.net [171.75.16.3] 12 2 0 101.13 107.45 104.29 ae6.6.ebr2.Washington111.level3.net [4.69.221.241] 13 2 0 102.06 109.10 105.58 ae41.41.ebr2.Washington12.level3.net [4.69.219.105] 14 2 0 100.84 103.20 102.02 ae2.3601.ear1.Washington12.level3.net [4.69.148.45] Target Name: 100ge0-36.core1.cle1.he.net IP: 184.104.192.202 Date/Time: 17.06.2024 01:13:14 - 17.06.2024 01:23:14 Hop Sent PL% Min Max Avg Host Name / [IP] 1 3 0 0.88 1.24 1.12 fritz.box [192.168.1.1] 2 3 0 4.51 59.22 22.95 p3e9bf597.dip0.t-ipconnect.de [62.155.245.xxx] 3 3 0 9.34 10.58 10.03 f-eh2-i.F.DE.NET.DTAG.DE [217.0.195.209] 4 1 0 79.33 79.33 79.33 e0-71.core3.fra2.he.net [184.104.226.69] 5 3 100 0 0 0 [-] 6 3 100 0 0 0 [-] 7 3 67 140.03 140.03 140.03 port-channel20.core3.nyc4.he.net [184.104.199.221] 8 4 0 101.14 129.55 108.51 100ge0-35.core2.phl1.he.net [184.104.193.214] 9 4 0 108.64 115.88 110.63 100ge0-36.core1.pit1.he.net [184.104.194.197] 10 4 0 110.55 116.07 112.25 100ge0-36.core1.cle1.he.net [184.104.192.202] Date Time Of Last Edit: 2024-06-17 09:32:51
|
| [2024-06-17 10:27:02] |
| nosast - Posts: 312 |
|
AT&T is not responding to ICMP but I will include Lumen and HE IPs for monitoring in my tool to have some longer term latency stats during market hours
|
| [2024-06-17 11:59:30] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Yes AT&T runs a very tight secure network. We could not figure anything out about their network, without asking them and having them run some trace routes, and pings for us.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-06-20 02:43:54] |
| User263711 - Posts: 30 |
|
From Singapore C:\Windows>tracert 184.104.192.202 Tracing route to 100ge0-36.core1.cle1.he.net [184.104.192.202] 3 3 ms 2 ms 2 ms bb42-61-207-254.singnet.com.sg [42.61.207.254] 6 2 ms 2 ms 2 ms 165.21.138.245 7 2 ms 2 ms 2 ms SN-SINQT1-BO403-ae1.singnet.com.sg [165.21.138.85] 8 6 ms 4 ms 5 ms 203.208.177.213 9 3 ms 2 ms 3 ms xn-lhrcl1-bo706.ix.singtel.com [203.208.183.81] 10 191 ms 172 ms 172 ms 203.208.173.22 11 * * * Request timed out. 12 182 ms 194 ms 181 ms port-channel16.core1.phx2.he.net [184.105.81.143] 13 * * * Request timed out. 14 254 ms 255 ms 254 ms port-channel18.core3.dal1.he.net [184.104.199.165] 15 254 ms 255 ms 253 ms 100ge0-35.core2.bna1.he.net [184.105.65.154] 16 257 ms * * 100ge0-74.core2.ind1.he.net [184.104.193.94] 17 237 ms 237 ms 236 ms 100ge0-35.core2.det1.he.net [184.104.192.201] 18 254 ms 254 ms * 100ge0-36.core1.cle1.he.net [184.104.192.202] 19 254 ms 254 ms * 100ge0-36.core1.cle1.he.net [184.104.192.202] 20 254 ms 254 ms 254 ms 100ge0-36.core1.cle1.he.net [184.104.192.202] Trace complete. C:\Windows>tracert 12.55.168.193 3 9 ms 3 ms 3 ms bb42-61-207-254.singnet.com.sg [42.61.207.254] 6 * * 2 ms 165.21.138.245 7 2 ms 2 ms 2 ms SN-SINQT1-BO403-ae1.singnet.com.sg [165.21.138.85] 8 3 ms 2 ms 2 ms 203.208.177.213 9 3 ms 3 ms 2 ms xn-lhrcl1-bo706.ix.singtel.com [203.208.183.81] 10 173 ms 172 ms 172 ms 203.208.172.154 11 * 182 ms 182 ms lag-2.mpr2.lax12.us.zip.zayo.com [64.125.35.201] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 204 ms 204 ms 204 ms ae28.mpr2.sea1.us.zip.zayo.com [64.125.29.103] 16 225 ms 225 ms * zayo-att.sea1.us.zip.zayo.com [64.125.13.94] 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. C:\Windows>tracert 4.69.148.45 Tracing route to ae2.3601.ear1.Washington12.level3.net [4.69.148.45] 3 15 ms 3 ms 2 ms bb42-61-207-254.singnet.com.sg [42.61.207.254] 6 * 2 ms 3 ms 165.21.138.245 7 2 ms 2 ms 2 ms SN-SINQT1-BO403-ae1.singnet.com.sg [165.21.138.85] 8 3 ms 2 ms 3 ms 203.208.177.213 9 22 ms 14 ms 37 ms 203.208.154.177 10 6 ms 3 ms 3 ms 203.208.146.10 11 3 ms 3 ms 3 ms ae9.3505.ebr1.Singapore3.level3.net [4.69.206.173] 12 84 ms 85 ms 85 ms ae3.3.ebr2.Tokyo4.level3.net [4.69.215.45] 13 87 ms 86 ms 86 ms ae1.11.ebr1.Tokyo4.level3.net [4.69.217.229] 14 198 ms 198 ms * ae17.17.ebr4.Seattle1.level3.net [4.69.215.205] 15 205 ms 205 ms 211 ms ae7.3.ebr6.Denver1.level3.net [4.69.203.238] 16 224 ms 224 ms 224 ms ae9.9.ebr1.KansasCity2.level3.net [4.69.227.37] 17 243 ms 244 ms 243 ms ae15.15.ebr2.Cleveland1.level3.net [4.69.226.201] 18 * 237 ms 236 ms ae1.11.ebr1.Cleveland1.level3.net [4.69.133.189] 19 247 ms * 246 ms ae5.5.ebr2.Washington12.level3.net [4.69.210.101] 20 245 ms 245 ms 245 ms ae2.3601.ear1.Washington12.level3.net [4.69.148.45] |
| [2024-06-20 15:24:37] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Thank you for this information.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-06-24 20:10:31] |
| BenjFlame - Posts: 324 |
|
In relation to the closing of this thread: Sierra Chart Internet Connectivity Related Issues What's the now default dsxx.sierracharts.com that is used when connecting from France ? I'd like to ping it from France to test the definitive setup you guys set. Date Time Of Last Edit: 2024-06-24 20:27:16
|
| [2024-06-24 22:06:03] |
| Sierra_Chart Engineering - Posts: 17154 |
|
You could test DS28.SierraCharts.com.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-06-25 08:31:11] |
| BenjFlame - Posts: 324 |
|
I get a good 87ms average. From across Atlantic I think this is as good as it gets. It goes trough cogent but it appears not to be a problem now and not something you can control. Also cogent picks up my route right here in France, and single handle it right to SC servers. That is also good. I notice I get also very good ping on DS32.SierraCharts.com . Can I use it to get the data ? How is the server used determined by SC, I see no mention of particular server in the message log ? Date Time Of Last Edit: 2024-06-25 08:54:55
|
| [2024-06-25 10:48:23] |
| Sierra_Chart Engineering - Posts: 17154 |
|
You can specify any server you want. This is fine. There are a list of servers provided to Sierra Chart and Sierra Chart simply iterates through them. For every category of data, there is a different server being used. And you will see the servers specified in the Message Log. You just have to look for them. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-06-25 10:48:40
|
| [2024-06-25 11:30:39] |
| BenjFlame - Posts: 324 |
|
In "CME Exchange Data Feed Server Address and Port Override:" there is no need to specify a port override, the server suffices ? Also I notice one of your server is in Germany (with of course a very good ping).... I guess there is no advantage to use it for CME products, and the direct route to Michigan is better ? |
| [2024-06-25 11:40:12] |
| nosast - Posts: 312 |
|
I think the server in Germany would be interesting to remove all the peering issues we experience and the route from Germany to CME could be handled routing-wise by SC. @BenjFlame: do you have the IP or name of this server in Germany? |
| [2024-06-25 12:23:12] |
| Sierra_Chart Engineering - Posts: 17154 |
|
No, the port number does not need to be specified. We can set up, a real-time relay for CME data on one of our servers in Germany but just be aware, if that server loses connectivity to our servers back in the US, then you will lose connectivity as well until that connectivity is restored. Normally this will not happen but it could happen and the connectivity could be lost for 30 seconds or so. This is generally the reason why we do not do it because it is just another intermediate connection that most often does not really help. We will work on that next week. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: