Support Board
Date/Time: Sun, 24 Nov 2024 03:33:28 +0000
Problems with Denali Data Feed
View Count: 3259
| [2024-02-08 18:53:44] |
| User330437 - Posts: 7 |
|
Dear Sierra Chart support, i have a servere Problem with the Deanali Data Feed for CME. It is extremely laggy and serverly slower than my CQG Data Feed i pay for as well. If i use the Deanli Data Feed it is literally impossible for me to trade, so i went back to using the older Versions of Sierra Chart so i can still use CQG, but i really want to switch to the Teton Order Routing service, so i have to get my Denali Data Feed into working order. i have tried everything i could, my Internet connection is very good ans stable, i tried to ping the Sierra Cahrt Servers and it shows no packet loss, but it is still laggy compared to other Data Feeds. Pls help me i am all out of ideas (i even tried to switch to linux to see if that fixes my Problem). Thank you for your help, Thomas |
| [2024-02-08 19:17:54] |
| John - SC Support - Posts: 36238 |
|
The main things to look at are listed at the following link: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often In addition to the above, we would like to see your Message Log to ensure there is not something else occurring. Please get us your Message Log by following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-08 19:43:08] |
| User330437 - Posts: 7 |
|
i have tried all the things i have found on your support forums, but sadly none work. my cpu usage is at 3-4% and the settings in my sierra chart work fine when i use version 2350 with cqg data, only the denali feed lags. i tried playing around with every single setting in the software for the last 4-5 mounths, but i cant fix it myself. i have send my message log for review |
| [2024-02-08 19:46:33] |
| John - SC Support - Posts: 36238 |
|
There is one big problem we see from your log. You have the setting for "Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Chart Data Feeds" set to "No". You need to change this to "Yes" and then select OK to close that window, then select "File >> Reconnect". After that, let us know how things are going. We will say though, we are surprised you were getting data at all, you should not have been. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-08 19:53:53] |
| User330437 - Posts: 7 |
|
i already switched the seting back to yes. i just turned it of to make sure the data is still fine with cqg at version 2350 before i wrote the support ticket. i have already switched back to version 2598 an turend to switched the allow sierra cahrt data back on .
|
| [2024-02-08 19:59:17] |
| User330437 - Posts: 7 |
|
i have recorded a video where you can see the difference in speed beetween my cqg data feed and my denali feed. if you want i can provide it for you
|
| [2024-02-08 21:09:39] |
| John - SC Support - Posts: 36238 |
|
The Message Log you provided does not give us the information we would need given what you have stated above. Please follow these instructions to get us your log: Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Close all of the Chartbooks with "File >> Close All Chartbooks". Open a single chart for the symbol you have an issue with through "File >> Find Symbol". Tell us that symbol of the chart. Tell us about *one* symbol only. Disconnect from the data feed with "File >> Disconnect". Connect to the data feed with "File >> Connect to Data Feed". After the connection and after about 1 minute, provide a copy of the Message Log following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We will then determine what the problem is. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-09 07:52:32] |
| User330437 - Posts: 7 |
|
i have sent you the requested mesage log, thank you for your help The symbol is ESH24. Date Time Of Last Edit: 2024-02-09 07:53:54
|
| [2024-02-09 09:20:35] |
| User330437 - Posts: 7 |
|
is there a way to chose the server i get my real time data from? i pinged all the data servers from this list (Data/Trading Service Connection and Symbol Issues: IP Addresses) and ds30.sierracharts.com shows the best latency and no packet loss, while some others show up to 15% packet loss. i found the CME exchange data feed server adress and port override setting, but i dont know if its the setting i am looking for and how to use it.
|
| [2024-02-09 15:29:03] |
| John - SC Support - Posts: 36238 |
|
There is nothing in the log that shows any issues, so it doesn't look like a major connectivity issue. There is not a way for you change which server you connect to. But, if you look at your log, you can see which server you are using, then if you select "File >> Reconnect" you will then be connected to a different server, so you can do this to connect to the specific one you want. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-09 16:14:02] |
| nosast - Posts: 312 |
|
User330437: are you also based in Europe? I have the same issues going on for months with Denali and switched to Rithmic until this gets solved for good. I tried everything and also different internet providers with no luck and currently thinking that it's caused by backbone-routing. Next step I'm trying is to get a VPS next to CHI and execute via remote desktop. Teton and Rithmic for example are rocksolid. Attached are screenshots from a few minutes ago when Nasdaq broke 18k. Date Time Of Last Edit: 2024-02-09 16:32:34
|
 SNAG_ 2024-02-09 - 17-06-00.png / V - Attached On 2024-02-09 16:13:19 UTC - Size: 31.96 KB - 125 views SNAG_ 2024-02-09 - 17-10-14.png / V - Attached On 2024-02-09 16:13:22 UTC - Size: 76.23 KB - 106 views SNAG_ 2024-02-09 - 17-09-47.png / V - Attached On 2024-02-09 16:13:38 UTC - Size: 73.15 KB - 98 views |
| [2024-02-11 04:44:10] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Yes they are in Europe. That IP address that starts with 64.125 that you are associating with Teton is not ours. For more information about the issue, refer to: Infrastructure Upgrades 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-02-11 04:45:53] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Do not change this: CME exchange data feed server adress and port override setting. Instead refer to: Infrastructure Upgrades 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-02-11 04:46:05
|
| [2024-02-11 13:06:20] |
| nosast - Posts: 312 |
|
That IP address that starts with 64.125 that you are associating with Teton is not ours.
I know but that is the last hop that answers to ping packets for my monitoring. |
| [2024-02-11 13:21:24] |
| nosast - Posts: 312 |
|
Attached is a traceroute from Germany. Shows the same like the example you mentioned from Portutal. It looks like a peering issue with Cogent or any other carrier involved in the route. Thanks for getting this sorted out - really looking forward to be able to trace the route back from Chicago to my location to see the full picture. Hop Sent PL% Min Max Avg Host Name / [IP] 1 453 0 2.05 40.83 5.32 fritz.box [192.168.1.1] 2 453 0 5.51 78.89 11.15 p3e9bf597.dip0.t-ipconnect.de [62.155.245.151] 3 453 0 10.80 341.82 37.05 f-ed12-i.f.de.net.dtag.de [217.5.94.226] 4 453 1 10.08 92.89 15.38 80.150.170.131 [80.150.170.131] 5 453 3 10.70 95.85 17.05 be3187.ccr42.fra03.atlas.cogentco.com [130.117.1.118] 6 453 0 17.48 122.13 24.28 be2814.ccr42.ams03.atlas.cogentco.com [130.117.0.141] 7 453 0 115.81 228.63 122.04 be12488.ccr42.lon13.atlas.cogentco.com [130.117.51.41] 8 453 0 122.15 187.65 125.90 be3488.ccr52.lhr01.atlas.cogentco.com [154.54.60.14] 9 453 0 119.70 179.69 124.85 be4325.ccr42.jfk02.atlas.cogentco.com [154.54.93.13] 10 453 0 122.06 191.65 126.58 be2890.ccr22.cle04.atlas.cogentco.com [154.54.82.245] 11 453 0 119.58 227.69 126.43 be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129] 12 453 0 119.98 178.02 123.78 be2248.ccr22.ord03.atlas.cogentco.com [154.54.5.158] 13 453 0 123.05 182.11 127.24 be2860.agr61.ord03.atlas.cogentco.com [154.54.87.62] 14 453 9 118.69 178.10 123.09 38.103.112.197 [38.103.112.197] Date Time Of Last Edit: 2024-02-11 13:26:37
|
| Screenshot 2024-02-11 at 14.15.53.png / V - Attached On 2024-02-11 13:19:33 UTC - Size: 647.37 KB - 104 views |
| [2024-02-12 15:44:53] |
| User330437 - Posts: 7 |
|
Thank you very much for your help. I am really looking forward to being able to finally use Teton.
Date Time Of Last Edit: 2024-02-12 17:16:33
|
| [2024-04-17 21:32:45] |
| nosast - Posts: 312 |
|
@Sierra_Chart Engineering Since a few days the peering issues with Cogent from/to Europe got worse again. After around 1pm central time Denali is way to laggy and stuttering. My monitoring shows lots of paketloss. Is there any news regarding the DC switch to Michigan and the feature to trace from DC to the users IP? (my ISP needs this to let me open support tickets). I would really love if you also use another carrier for the main connection. Cogent caused the issues some users had in February as they withdrew peering with NTT. wikipedia states: In February 2024, Cogent withdrew peering with NTT in Europe,[33][34] forcing all their peering traffic to go through their common remaining interconnections in USA, increasing latency and traffic loss between both networks, to complain against refusal of peering settlements in Asia from NTT. https://en.wikipedia.org/wiki/Cogent_Communications#Peering_disputes Date Time Of Last Edit: 2024-04-18 20:35:45
|
| [2024-04-17 22:09:11] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Allow about four more weeks, before another ISP is added. We are getting very close to doing that. And we will bring this posting to the new ISP they can comment on it. 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-04-17 23:06:46] |
| Sierra_Chart Engineering - Posts: 17154 |
|
The move to Michigan will be completed in about two months: Is there any news regarding the DC switch to Michigan and the feature to trace from DC to the users IP?
We had other higher priorities affecting, adding the trace route functionality. 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-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 |
| [2024-05-28 23:27:46] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Zayo has been decided against, because they are simply going to take the traffic to right back to literally 350 E. Cermak in Chicago. So that is not what we are going to do. We need carriers who are going to go eastward for traffic to/from Europe. Not back to Chicago. We have spent quite a bit of time investigating this. 123 net gives us a solution, in the next few days, with connectivity to the following.: Lumen AS209 Chicago, IL
Cogent AS174 Southfield, MI GTT AS3257 Chicago, IL Hurricane Electric AS6939 Southfield, MI Lumen AS3356 Southfield, MI NTT Communications AS2914 Chicago, IL PCCW Global AS3491 Chicago, IL Tata Communications AS6453 Ashburn, VA Arelion AS1299 Southfield, MI Verizon AS2828 Southfield, MI 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.
The location that they are at which is relevant in this case is the 24700 Northwestern Highway address. All of the major carriers are in that building as well as the Detroit Internet exchange. So the connectivity, is right within that building where we are located. And it goes eastward from there. There is no latency impact since it is along the way from Chicago.Cogent is going to be removed. They have completely breached the contract and deliberately did harm to our users, for their own selfish interest. We had not truly understood what was going on with them regarding peering relationships until about the last 5 days or so. If we use AT&T, we see the connection is going from, Michigan to New York, then over to Deutsche Telekom in Germany. Looks very direct. Not sure if you are able to evaluate how the connection would be if we use AT&T. We have asked them for an IP, that we can use for a trace route but they declined to provide one. 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-05-28 23:30:04
|
| [2024-05-29 08:11:08] |
| nosast - Posts: 312 |
|
If we use AT&T, we see the connection is going from, Michigan to New York, then over to Deutsche Telekom in Germany. Looks very direct. Not sure if you are able to evaluate how the connection would be if we use AT&T. We have asked them for an IP, that we can use for a trace route but they declined to provide one.
I found an IP-Probe that is related to AT&T in Detroit (but not sure which DC it resides). The traffic is routed from Deutsche Telekom to AT&T Washington and then to Detroit (hops in between are unknown) but add around 20ms from Washington to Detroit which seems odd. For sure this is only a rough estimate - without the real IP from AT&T in Southfield it's tough to say. 3 8 0 103.11 104.00 103.64 was-sa2-i.was.us.net.dtag.de [62.154.5.106] 4 8 0 104.28 107.32 105.89 192.205.34.185 [192.205.34.185] 5 8 100 0 0 0 [-] 6 8 100 0 0 0 [-] 7 8 100 0 0 0 [-] 8 8 100 0 0 0 [-] 9 8 0 122.58 123.74 122.93 32.130.18.137 [32.130.18.137] 10 8 0 122.53 124.02 123.10 71.151.213.101 [71.151.213.101] 11 8 100 0 0 0 107-137-82-44.lightspeed.livnmi.sbcglobal.net [107.137.82.44] But on the DET-IX's website all the IPs are stated from all the participants so I traced right to 123.net IP in Southfield. The trace looks perfect and the routing is via Lumen (Level3) which is for sure one of the best carriers. Only 6 Hops from my PC to DET-IX. 3 41 0 8.99 10.78 9.75 f-eh1-i.f.de.net.dtag.de [217.5.116.250] 4 31 97 8.74 8.74 8.74 193.158.39.70 [193.158.39.70] 5 41 0 108.05 119.83 110.25 ae8.8.bar3.detroit1.level3.net [4.69.143.253] 6 41 100 0 0 0 static.det-ix.net [209.124.52.123] Date Time Of Last Edit: 2024-05-29 08:12:02
|
| [2024-05-29 12:59:15] |
| Sierra_Chart Engineering - Posts: 17154 |
|
We will try to get AT&T to run a trace route to your location. What IP should we use? Lumen is no problem for us to add. Although we will have access to Lumen, on Friday, when our connection with 123.net becomes operational. Although we might not have it operational until Monday. We will see. You say 6 hops to the Detroit Internet exchange, but between the beginning and ending point we see just 2 switch points. So total of four. How do you calculate six? 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-05-29 13:02:35
|
| [2024-05-29 13:20:47] |
| nosast - Posts: 312 |
|
As I have a dynamic IP it would be best to trace to 217.5.116.250 Deutsche Telekom backbone. Out of the 6 hops I striped out 2 in the beginning (my internal IP and the WAN-router). Here is the full trace: Hop Sent PL% Min Max Avg Host Name / [IP] 1 226 0 0.65 4.44 1.12 fritz.box [192.168.xxxx] 2 226 0 3.94 66.79 6.65 xxxxxx.dip0.t-ipconnect.de 3 226 0 8.95 56.56 10.56 f-eh1-i.f.de.net.dtag.de [217.5.116.250] 4 226 100 9.15 9.15 9.15 193.158.39.70 [193.158.39.70] 5 226 0 107.88 154.43 112.21 ae8.8.bar3.detroit1.level3.net [4.69.143.253] 6 226 100 0 0 0 static.det-ix.net [209.124.52.123] |
| [2024-05-29 21:49:58] |
| nosast - Posts: 312 |
|
@Sierra_Chart Engineering Trace from Europe to your server in Southfield (DS32): Hop Sent PL% Min Max Avg Host Name / [IP] 3 136 0 8.65 12.72 9.66 f-ed12-i.F.DE.NET.DTAG.DE [217.0.198.221] 4 136 0 8.16 74.51 9.50 80.150.170.131 [80.150.170.131] 5 136 0 8.11 72.77 11.38 be3187.ccr42.fra03.atlas.cogentco.com [130.117.1.118] 6 136 4 15.34 108.25 18.13 be5160.ccr41.ams03.atlas.cogentco.com [130.117.3.66] 7 136 5 25.17 33.60 26.10 be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77.246] 8 136 0 100.64 170.04 102.54 be3042.ccr21.ymq01.atlas.cogentco.com [154.54.44.162] 9 136 0 104.60 185.14 106.55 be3259.ccr31.yyz02.atlas.cogentco.com [154.54.41.205] 10 136 0 102.26 138.35 103.71 be2993.ccr21.cle04.atlas.cogentco.com [154.54.31.225] 11 136 0 104.79 106.89 106.13 be3744.rcr51.tol01.atlas.cogentco.com [154.54.0.146] 12 136 0 107.19 114.54 108.11 be2123.rcr21.dtw04.atlas.cogentco.com [154.54.82.138] 13 136 0 107.51 108.91 108.08 DS32.sierracharts.com [38.103.85.68] Looks like peering via Cogent is the main route the pakets use right now. Paketloss of 4 and 5 percent at hop 6 and 7 already visible (still in Europe before crossing the atlantic). Are you able to deactivate the Cogent route in the DC to use one of the other carriers? Arelion, NTT and Lumen should offer the best global peering afaik. Date Time Of Last Edit: 2024-05-29 21:55:53
|
To post a message in this thread, you need to log in with your Sierra Chart account: