Support Board
Date/Time: Sun, 24 Nov 2024 03:48:21 +0000
Problems with Denali Data Feed
View Count: 3260
| [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
|
| [2024-05-29 22:01:18] |
| Sierra_Chart Engineering - Posts: 17154 |
|
We have not yet made the change! The change has not gone into effect yet! We were clear about that: is going to be available we expect tonight.
You can use it for CME data by using the server DS32.sierracharts.com We will let you know when it actually goes into effect. You may want to wait because Internet connectivity will be interrupted to the server for a period of time. 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-29 22:05:59] |
| nosast - Posts: 312 |
|
Yeah I read that and have not done any changes to my SC. Just traced the IP and saw that it's routed to DTW Detroit. I will check later after you finished the setup. Apologies! Date Time Of Last Edit: 2024-05-29 22:06:21
|
| [2024-05-29 22:38:13] |
| Sierra_Chart Engineering - Posts: 17154 |
|
We cannot make the change this evening. We need more information from the ISP.
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-30 04:52:35] |
| Amelyn - Posts: 44 |
|
We need a temporary solution immediately. Regardless of who's at fault, we trust and pay for Sierrachart yet this is the second major incident in recent months, the previous one being an inability to use alerts for several weeks.
Date Time Of Last Edit: 2024-05-30 04:52:49
|
| [2024-05-30 08:05:03] |
| Sierra_Chart Engineering - Posts: 17154 |
|
We will have a temporary solution for CME data, ready in about 30 minutes for you. this is the second major incident in recent months, the previous one being an inability to use alerts for several weeks. We strongly disagree with this. And it is not true! What you are referring to is email alerts, and there is always the potential for problems with email alerts and always has been especially when there is abuse by users. There is no guarantee you are going to get email alerts at all. There never has been. And it was not weeks. We actually had an alternative ready in three days. We are never going to accept fault, for email alert delivery. Do not fault us for issues like that. We have every right to cut off email alerts when there is abuse by users damaging our reputation. It was not several weeks. It was three days: Notice: Sierra Chart Alert App and Telegram Replacing Email/SMS Alerts Email delivery of alerts has been an ongoing issue for us, always. It should never have been regarded as a reliable method of alert delivery. And never was. A custom application which we now have developed, and uses a direct connection to our server is the only reliable method.: Chat and Communications Platform: Web-Based/Mobile Chat Application 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-30 08:45:17
|
| [2024-05-30 08:35:23] |
| Sierra_Chart Engineering - Posts: 17154 |
|
This is a temporary server you can use for the time being and only use it if you absolutely need to. We have limited bandwidth available on the server. ds21.sierracharts.com Enter the server address, in this field: Sierra Chart Server Settings: CME Exchange Data Feed Server Address and Port Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) (CME Exchange Data Feed Server Address and Port Override) Make sure you are running an up-to-date version of Sierra Chart. Instructions: Software Download: Fast Update This only applies to CME data. Not to other exchanges. It also does not apply to historical data either. Just real-time data. 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-30 10:10:22] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Nosast, Can you please run a ping and trace route, to this IP: 216.234.102.193 From your location and get us the results ASAP. And we want to know, how the ping looks at 9:30 AM Eastern time to see if there is any packet loss. 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-30 10:40:49
|
| [2024-05-30 12:49:26] |
| nosast - Posts: 312 |
|
Below is the trace (peering via GTT) Target Name: 216-234-102-193.static.123.net
IP: 216.234.102.193 Date/Time: 30.05.2024 14:37:46 - 30.05.2024 14:47:46 Hop Sent PL% Min Max Avg Host Name / [IP] 1 47 0 0.50 1.23 0.86 [192.168.1.1] 2 47 0 3.93 15.51 5.44 xxxxx.dip0.t-ipconnect.de [62.155.245.xxx] 3 47 0 9.97 11.72 10.62 m-ef2-i.M.DE.NET.DTAG.DE [217.5.94.146] 4 47 0 9.15 11.26 10.23 m-ef2-i.M.DE.NET.DTAG.DE [217.5.94.146] 5 47 0 13.08 185.22 24.59 80.150.168.185 [80.150.168.185] 6 47 0 103.46 210.21 107.09 ae5.cr1-det3.ip4.gtt.net [89.149.143.133] 7 47 0 111.74 118.49 113.37 ip4.gtt.net [66.171.226.42] 8 47 0 110.97 112.12 111.41 216-234-102-193.static.123.net [216.234.102.193] I have this IP in my monitoring an will report after the RTH open Date Time Of Last Edit: 2024-05-30 12:51:21
|
| [2024-05-30 13:18:29] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Ok thank you. We have since learned that this is not going to be the IP that we will be using. It is a different one but we do not yet have a switch yet connected that will respond to a ping on the one that we will be using. That will not happen until this evening. Our new subnet is 67.214.125.0/28 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-30 13:28:24] |
| nosast - Posts: 312 |
|
Alright. Let me know if you need a trace/monitoring. The subnet currently uses the same route via GTT. Target Name: 67.214.125.0
IP: 67.214.125.0 Date/Time: 30.05.2024 15:17:14 - 30.05.2024 15:27:14 Hop Sent PL% Min Max Avg Host Name / [IP] 1 23 0 0.49 9.94 2.86 [192.168.1.1] 2 23 0 3.94 12.08 5.89 xxx.dip0.t-ipconnect.de [62.155.245.xxx] 3 23 0 10.43 20.95 12.11 m-ef2-i.M.DE.NET.DTAG.DE [217.5.94.110] 4 23 0 9.59 23.24 13.36 m-ef2-i.M.DE.NET.DTAG.DE [217.5.94.110] 5 23 0 12.73 23.34 14.98 80.150.168.185 [80.150.168.185] 6 23 0 104.72 206.93 110.13 ae5.cr1-det3.ip4.gtt.net [89.149.143.133] 7 23 0 113.01 124.81 116.88 ip4.gtt.net [66.171.226.42] 8 23 0 108.52 118.67 110.91 67.214.125.193 [67.214.125.193] 9 23 100 0 0 0 67.214.125.0 [67.214.125.0] For the time being I put in 67.214.125.193 into my monitoring. This IP responds to ICMP. Date Time Of Last Edit: 2024-05-30 21:28:55
|
| [2024-06-01 14:37:23] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Here is the current trace route to your IP in Germany from our new network connection in Michigan: Tracing route to f-eh1-i.F.DE.NET.DTAG.DE [217.5.116.250]
over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.10.20.1 2 <1 ms <1 ms <1 ms 216-234-102-193.static.123.net [216.234.102.193] 3 1 ms <1 ms <1 ms 69-39-66-242.static.123.net [69.39.66.242] 4 11 ms 11 ms 11 ms 63.243.136.49 5 12 ms 11 ms 12 ms if-bundle-54-2.qcore1.aeq-ashburn.as6453.net [216.6.87.84] 6 21 ms 21 ms 21 ms 80.156.160.86 7 12 ms 12 ms 12 ms was-sa3-i.WAS.US.NET.DTAG.DE [62.154.5.230] 8 95 ms 94 ms 94 ms mrs-sa1-i.MRS.FR.NET.DTAG.DE [62.154.5.234] 9 100 ms 100 ms 100 ms s-sa4-i.S.DE.NET.DTAG.DE [217.239.52.150] 10 103 ms 103 ms 103 ms f-eh1-i.F.DE.NET.DTAG.DE [217.5.116.250] Trace complete. So 123Net is peering with Tata Communications in Ashburn Virginia then to Deutsche Telekom within the US and then over the Atlantic subsea cables into France and then on to Germany. Looks very good. And for the record, it is 3.5 ms one way between Aurora Illinois where the data originates from in the CME DC, to Southfield Michigan. And there are changes, with buffer timing that we can make, to fully negate that 3.5 ms. This has been planned. However, in the case of anyone east of Chicago, this extra time is always going to be there anyway. 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-01 14:44:22
|
| [2024-06-01 16:38:52] |
| nosast - Posts: 312 |
|
I don't have any experience with Tata as Tier1 Carrier but the ping and trace from my site also looks good. If I trace to the Tata Core Router 63.243.136.49 the pakets are routed from Deutsche Telekom to Tata Backbone in Frankfurt and from there on don't leave Tata until peering to 123.net. If I trace 216.234.102.193 the peering is from Deutsche Telekom via GTT but also with good stats. |
| [2024-06-01 17:52:07] |
| Sierra_Chart Engineering - Posts: 17154 |
|
The handover of packets, is in Ashburn Virginia in the United States direct to Deutsche Telekom from Tata. Deutsche Telekom is carrying the packets over the Atlantic. This is of course the traffic going from our server out to your computer. ip:"62.154.5.230",
hostname:"was-sa3-i.was.us.net.dtag.de", city:"Ashburn", region:"Virginia", country:"US", loc:"39.0437,-77.4875", org:"AS3320 Deutsche Telekom AG", 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-01 17:54:59
|
| [2024-06-01 18:32:06] |
| nosast - Posts: 312 |
|
Yeah sure. It's not uncommon that the "way back" uses another route. But most important in this case is the traffic delivered from your server to my SC client.
Date Time Of Last Edit: 2024-06-01 18:38:39
|
| [2024-06-02 13:32:57] |
| BenjFlame - Posts: 324 |
|
I'm from France, if you need ping/tracert please tell. I too was subject to the packet loss issue. I reported about that a while ago (Connexion lost on several occasions today december 5).
Date Time Of Last Edit: 2024-06-02 13:56:37
|
| [2024-06-02 14:16:55] |
| Sierra_Chart Engineering - Posts: 17154 |
|
No, we do not need this information. Just restart Sierra Chart to get the updated address list. We could not get a clear trace route to your IP. 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-02 15:29:08] |
| BenjFlame - Posts: 324 |
|
What's the tracert destination I can test to see the route it takes from France => new service?
Date Time Of Last Edit: 2024-06-02 15:29:27
|
| [2024-06-02 16:02:21] |
| Sierra_Chart Engineering - Posts: 17154 |
|
tracert ds32.sierracharts.com We tried tracing from the server to your IP but there was no useful information. Most of the switches did not respond. But we can see, that the data is going to be routed through Ashburn Virginia. Initially through Tata. After that there was no response. 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-02 16:03:11
|
| [2024-06-02 16:32:41] |
| BenjFlame - Posts: 324 |
|
I can ping with no packet loss, but indeed the traceroute has many failures. Wasn't the route from European customer supposed not to go through cogent anymore? C:\Users\webko>tracert ds32.sierracharts.com 1 <1 ms <1 ms <1 ms livebox.home [192.168.xx] 2 2 ms 2 ms 2 ms 80.xx.xxxx 3 2 ms 2 ms 1 ms ae108-0.ncidf203.rbci.orange.net [193.249.212.102] 4 2 ms 2 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 78 ms 98 ms be3628.ccr42.jfk02.atlas.cogentco.com [154.54.27.169] 9 91 ms 90 ms 90 ms 154.54.162.169 10 * * * Request timed out. 11 95 ms 94 ms 94 ms be2123.rcr21.dtw04.atlas.cogentco.com [154.54.82.138] 12 90 ms 91 ms 91 ms gi0-0-0-18.204.nr11.b015471-1.dtw04.atlas.cogentco.com [38.122.60.13] 13 88 ms 87 ms 88 ms 67.214.125.193 14 87 ms 87 ms 87 ms 67.214.125.3 |
| [2024-06-02 16:40:22] |
| Sierra_Chart Engineering - Posts: 17154 |
|
We cannot control that. That is all controlled by BGP routing. We cannot eliminate Cogent from the route if that is how it's being routed. Try changing to a different ISP on your side. Your ISP, is who is controlling that. Not us. We have no control over that at all. And Cogent is not necessarily bad. Some users would be affected by de-peering they have done but most not. What users need to realize is that it is fully impossible, for us to ever guarantee complete reliability with communication over the public Internet. It is just simply impossible. And most problems users encounter, is not even attributable to the connectivity from our side. You are going to have problems at times. If you have ongoing issues look at changing your ISP. Just like we are adding additional 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-02 17:13:36
|
| [2024-06-03 07:29:13] |
| Amelyn - Posts: 44 |
|
I've updated Sierrachart and followed instructions. Still downloading data at 10% of the normal speed. A watchlist that historically takes 10 minutes to download is still going 1 hour later.
|
| [2024-06-03 08:02:19] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Due to how historical data requests work where there is a separate connection for each request, this can be a problem. So in your particular case, you need to set this setting: Sierra Chart Server Settings: CME Exchange Data Feed Server Address and Port Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) and this following setting: Sierra Chart Server Settings: CME Exchange Data Feed Historical Server Address Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) to: ds32.sierracharts.com This will not be needed, after about two weeks from now. 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-03 08:03:30
|
| [2024-06-06 18:43:13] |
| nosast - Posts: 312 |
|
I switched do DS32 today but have experienced disconnects from the datafeed and paketloss starting at the hop GTT in Detroit right now. Is DS32 ready to use live yet? Pingplot attached. Date Time Of Last Edit: 2024-06-06 19:08:01
|
 SNAG_ 2024-06-06 - 20-42-45.png / V - Attached On 2024-06-06 18:43:07 UTC - Size: 41.5 KB - 72 views SNAG_ 2024-06-06 - 20-44-12.png / V - Attached On 2024-06-06 18:44:51 UTC - Size: 144.5 KB - 59 views |
| [2024-06-06 19:56:20] |
| Sierra_Chart Engineering - Posts: 17154 |
|
What time zone is that? That server and network is absolutely ready for live use. You also need to understand that we have no control over the path from your computer back to our network. This is that what we see: Tracing route to f-eh1-i.F.DE.NET.DTAG.DE [217.5.116.250]
over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.10.20.1 2 <1 ms <1 ms <1 ms 216-234-102-193.static.123.net [216.234.102.193] 3 <1 ms <1 ms <1 ms 69-39-66-242.static.123.net [69.39.66.242] 4 12 ms 11 ms 11 ms 63.243.136.49 5 11 ms 11 ms 11 ms if-bundle-54-2.qcore1.aeq-ashburn.as6453.net [216.6.87.84] 6 21 ms 21 ms 21 ms 80.156.160.86 7 13 ms 12 ms 12 ms was-sa3-i.WAS.US.NET.DTAG.DE [62.154.5.230] 8 95 ms 95 ms 94 ms mrs-sa1-i.MRS.FR.NET.DTAG.DE [62.154.5.234] 9 100 ms 100 ms 100 ms s-sa4-i.S.DE.NET.DTAG.DE [217.239.52.150] 10 103 ms 103 ms 103 ms f-eh1-i.F.DE.NET.DTAG.DE [217.5.116.250] First Cogent is being faulted now GTT. We do not have control over this. We would recommend contacting Deutsche Telekom about this. If there is a problem with the return path from your computer to our network, that is an issue because the packet acknowledgments are not being received and being dropped. This absolutely will cause a data feed to stop and there will be disconnections. 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-06 20:04:29
|
| [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. |
To post a message in this thread, you need to log in with your Sierra Chart account: