Support Board
Date/Time: Sun, 24 Nov 2024 07:41:24 +0000
Post From: Infrastructure Upgrades
| [2024-02-11 02:37:06] |
| Sierra_Chart Engineering - Posts: 17154 |
|
---- Denali Data Feed: Starting last week, starting to February 2, 2024, we have had some users in Europe reported degradation with the Denali Data Feed. First we want to make it very clear, there is no problem, with our source data feeds for the Denali Data Feed which originate from the exchanges. There is no problem with the market data processing. This is all very efficient. There is no problem with our servers. There is no problem with our network equipment. There is no problem with our network connectivity. There is no problem with our ISP Cogent, in Chicago or the United States. Everything is working perfectly. There are no issues with degradation of data delivery within the US, or in the Asia-Pacific area. This is strictly a problem some users have in Europe only. The primary way we are going to address this, is adding an additional ISP and also reporting the issue to Cogent. This new ISP, will be in our new location space in Michigan. This location should become initially operational in about a month. Refer to this help topic, to the extent you can resolve this yourself: Prices / Data Falling Behind: 4.12 - Sierra Chart Exchange Data Feeds ----- One of our users in Portugal, has raised issues receiving the Denali Data Feed, on February 2, 2024. Their graphs showed Cogent all the way to their ISP. From our side, we show Cogent and Tata Communications. See below. So the return packet acknowledgments which are essential for the data flow from the Sierra Chart network to their computer are taking a different route. The problem could be with Tata Communications. Tracing route to po1-84-90-251-139.netvisao.pt [84.90.251.139] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.10.20.4 2 * * * Request timed out. 3 1 ms 1 ms <1 ms be2051.ccr41.ord03.atlas.cogentco.com [154.54.84.49] 4 1 ms 1 ms 1 ms be2766.ccr42.ord01.atlas.cogentco.com [154.54.46.177] 5 7 ms 7 ms 7 ms be2718.ccr22.cle04.atlas.cogentco.com [154.54.7.130] 6 19 ms 19 ms 19 ms be2890.ccr42.jfk02.atlas.cogentco.com [154.54.82.246] 7 19 ms 19 ms 19 ms be3295.ccr31.jfk05.atlas.cogentco.com [154.54.80.2] 8 18 ms 18 ms 18 ms tata.jfk05.atlas.cogentco.com [154.54.12.18] 9 * 119 ms 120 ms if-ae-32-3.tcore2.ldn-london.as6453.net [80.231.20.106] 10 * * * Request timed out. 11 119 ms 119 ms 119 ms if-ae-19-2.tcore1.sv8-highbridge.as6453.net [80.231.138.21] 12 117 ms 117 ms 118 ms if-ae-1-3.tcore1.pv9-lisbon.as6453.net [80.231.158.29] 13 117 ms 123 ms 123 ms if-ae-2-2.tcore2.pv9-lisbon.as6453.net [80.231.158.6] 14 110 ms 110 ms 111 ms 80.231.159.46 15 111 ms 110 ms 110 ms 10.170.128.5 16 112 ms 112 ms 112 ms pa1-84-91-1-222.netvisao.pt [84.91.1.222] 17 * * * Request timed out. 18 * * * Request timed out. ---- For Cogent to troubleshoot this type of an issue they require at the time of an incident both a ping and a trace route in both directions. It is difficult for us to gather this information for individual users when there is a problem. What we are going to do, is in our new colocation space in Michigan, we are going to add a Web server there for you to be able to run ping and trace route, from that location to your IP. Then you can gather all the information and give it to us and then we can give it to Cogent or other ISPs whichever one is being used. 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:42:58
|