Support Board
Date/Time: Mon, 16 Mar 2026 20:21:27 +0000
CME Data Freezing
View Count: 2372
| [2026-03-11 14:57:16] |
| OrderFlow - Posts: 31 |
|
Same here with frequent 3 second data freezes this morning.
|
| [2026-03-12 01:41:58] |
| joshtrader - Posts: 541 |
|
Something that may be interesting here. I run two SC instances. One freezes (as it did today, for 3 seconds at a time, in the morning a few times) and is version 2874. It uses Denali data but Rithmic routing. The other has not frozen that I can remember, it keeps ticking, and is version 2803, and has "SC Data" (Denali only) with no order routing of any kind. It's quite old at this point but has had no issues with freezing.
|
| [2026-03-12 02:52:41] |
| User509533 - Posts: 97 |
|
FYI: No issues today. Running version 2882 (using the Sierra Chart timer with a 10 ms update interval and Sierra Chart’s NTP server).
|
| [2026-03-12 15:25:03] |
| Sierra_Chart Engineering - Posts: 23225 |
|
Yesterday, March 11 we did not notice the data feed stopping. And we did monitor it at the open (9:30 AM Eastern time). We were looking at NQ index futures. It definitely did not stop. But we were not checking, every server and every connection, because we do have a lot of servers and Internet connections. We did notice a delay of about a second at the open but this is hard to avoid with extreme activity. Nevertheless we will see how to improve upon that. We did not notice, any data delays today or a stopping data feed, and we were monitoring more than one server this time. In general about a stopping data feed or data delays, refer to: Prices / Data Falling Behind: 4.21 - Why a Data Feed Stops or Becomes Delayed (This is a very important section to read!) The other thing we want to point out, is that this thread was started, due to a problem, that has been definitively resolved and will never happen again. Data feed stopping issues which are still occurring, are explained in the above link. It is unrelated to the original problem. Nevertheless, we still are doing some improvements, with connectivity and infrastructure. Whether this makes any difference or not we do not know. In many cases it will not make any difference. In some cases it might. 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: 2026-03-12 15:32:10
|
| [2026-03-12 15:36:27] |
| Sierra_Chart Engineering - Posts: 23225 |
|
Regarding post #76, the version of Sierra Chart is unlikely to be relevant. It is likely connected to a different Internet connection and server that we have.
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 |
| [2026-03-12 15:44:14] |
| Sierra_Chart Engineering - Posts: 23225 |
|
I ran an endless ping test to sierrachart.com, and when the lag/freezing would occur in the DOM, I would also get a timed out message in my ping test. To the extent this would be at our side, could only be related, to a network switch, that is handling data rates and packets beyond its capacity. We would think this would be very unlikely. If that were the case, there would be a lot more constant ongoing problems and there just are not. Otherwise, the problem would simply be due to an ISP issue, or somewhere else in the path of communication between your computer and the server which we have no control over. 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 |
| [2026-03-12 15:48:43] |
| Sierra_Chart Engineering - Posts: 23225 |
|
Just to let you know that your ISP Lumen servers are not working well today, namely e.g. IP 4.69.143.253 Server name: ae8.8.bar3.Detroit1.net.lumen.tech, among other Lumen servers.
To be clear, the problem is not with the servers. It has to do with the ISP used for those servers which is at a completely separate layer away from the server. This is at the routing layer.Your servers affected are DS26, DS31-2, ds25-2, ds26-2 and possibly a few more. These Lumen servers are constantly failing and causing package loss. This is not a normal situation at all, they have been working well. I hope this information helps you to resolve the problem with the ISP. Now we understand the reason for the problem. Probably the issue was simply with Lumen and we have no control over that. This is going to happen from time to time! Nothing we can do about it. Now it is clear the problem was likely with Lumen. Interesting, we are getting two additional circuits from them. They are overall a very good provider. 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: 2026-03-12 15:49:48
|
| [2026-03-12 16:04:28] |
| Rui S - Posts: 220 |
|
They are overall a very good provider.
Yes, for my location they are the best you work with. There is nothing for us to resolve. We do not contact an ISP about these transient issues. Only if there is an ongoing persistent issue. ISPs have problems all the time and they detect them and correct them.
I did let you know for you to be aware of the issue and also because once you told me to let you know when issues like this happen, so you could contact the ISP. Date Time Of Last Edit: 2026-03-12 16:05:10
|
| [2026-03-12 21:30:07] |
| Sierra_Chart Engineering - Posts: 23225 |
|
I did let you know for you to be aware of the issue and also because once you told me to let you know when issues like this happen, so you could contact the ISP.
Yes thank you. We would not report an incident like this to the ISP. These are just transient problems which come and go. If there is an ongoing problem we would.We have another Internet circuit, from the data center, which is underutilized and we are going to put a new server we brought recently online DS7.SierraCharts.com, on that connection this evening. We are working on this 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: 2026-03-12 21:31:42
|
| [2026-03-13 10:52:31] |
| Rui S - Posts: 220 |
|
We would not report an incident like this to the ISP. These are just transient problems which come and go. If there is an ongoing problem we would.
Thank you for your reply. However, I think you didn't quite understood the intent of my message on my post #70 that day. It really was an ongoing problem that was severely affecting the performance of all Denali servers that were connected through that ISP during several hours. I assumed I should alert you of that. Please take a look at the file attached. I assure you that I have the means and knowledge to fully differentiate a generalized problem from a normal transient problem, which occur very often, as you say. In any case, what is important is the issue was resolved and everything is back to normal since that day. |
Private File |
To post a message in this thread, you need to log in with your Sierra Chart account: