Support Board
Date/Time: Fri, 01 May 2026 18:25:53 +0000
CME Data Freezing
View Count: 3417
| [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: 543 |
|
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: 23657 |
|
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: 23657 |
|
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: 23657 |
|
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: 23657 |
|
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: 234 |
|
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: 23657 |
|
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: 234 |
|
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 |
| [2026-04-01 13:13:16] |
| Rui S - Posts: 234 |
|
Sierra Chart Support, I think you should know that lately, every time that there is a significant market acceleration (e.g. when Mr. Trump tweets or "speaks"), there is an overload on the data feed causing it to freeze for several seconds (15 seconds or more) and then it keeps stuttering for a while. Last two times were yesterday between 12:38 and 12:41pm EST and today between 8:44 and 8:45pm EST. I can assure it's definitely not an internet issue as I'm always monitoring it. Also, the Denali servers keep responding normally to the pings during those periods, so maybe it is some kind of choking before the Denali servers or lack of capacity from CME, I don't know. I thought you should know. |
| [2026-04-01 13:41:40] |
| 284630 - Posts: 15 |
|
I fully agree with the details Rui observed. This was also what I felt when I first read this thread—when volatility accelerates, the Denali data source experiences lag. This performance issue could be due to insufficient memory queues or CPU processing capacity, but the specific cause can only be identified through monitoring and troubleshooting by engineers. I really hope this can draw the attention of the Sierra development team.
|
| [2026-04-01 14:27:34] |
| Sierra_Chart Engineering - Posts: 23657 |
|
We have not observed this: I think you should know that lately, every time that there is a significant market acceleration (e.g. when Mr. Trump tweets or "speaks"), there is an overload on the data feed causing it to freeze for several seconds (15 seconds or more) and then it keeps stuttering for a while. We have observed, some lag in some cases but not all, of about a second or two, and we are working on isolating that and resolving it. Last two times were yesterday between 12:38 and 12:41pm EST and today between 8:44 and 8:45pm EST. We will check the logs.
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-04-01 14:34:18] |
| Sierra_Chart Engineering - Posts: 23657 |
|
This is the logging from one of our main distribution servers, the other distribution server will be about the same. One thing to understand about this logging, is only delays of 50 milliseconds and greater, are recorded. If they are lower they are not logged. What we are interested in is a lag. And there is never going to be a stopping data feed at this point. There is no data delay or interruption occurring. All times are UTC. 2026-03-31 16:37:49.932 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.278 2026-03-31 16:37:51.150 | ESM26-CME[M] Daily #1 | Data Delay (ms): 78.229 2026-03-31 16:37:51.150 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.11 2026-03-31 16:37:52.369 | ESM26-CME[M] Daily #1 | Data Delay (ms): 78.229 2026-03-31 16:37:52.370 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.11 2026-03-31 16:37:57.245 | NQM26-CME[M] Daily #2 | Data Delay (ms): 54.03 2026-03-31 16:37:59.682 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.532 2026-03-31 16:37:59.683 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.084 2026-03-31 16:38:00.901 | ESM26-CME[M] Daily #1 | Data Delay (ms): 56.051 2026-03-31 16:38:00.902 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.084 2026-03-31 16:38:02.120 | ESM26-CME[M] Daily #1 | Data Delay (ms): 56.051 2026-03-31 16:38:02.120 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.922 2026-03-31 16:38:05.777 | ESM26-CME[M] Daily #1 | Data Delay (ms): 72.047 2026-03-31 16:38:05.777 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.833 2026-03-31 16:38:09.435 | ESM26-CME[M] Daily #1 | Data Delay (ms): 53.205 2026-03-31 16:38:11.872 | ESM26-CME[M] Daily #1 | Data Delay (ms): 57.931 2026-03-31 16:38:11.873 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.963 2026-03-31 16:38:13.092 | ESM26-CME[M] Daily #1 | Data Delay (ms): 53.11 2026-03-31 16:38:13.092 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.963 2026-03-31 16:38:14.311 | ESM26-CME[M] Daily #1 | Data Delay (ms): 53.11 2026-03-31 16:38:15.529 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.037 2026-03-31 16:38:17.967 | ESM26-CME[M] Daily #1 | Data Delay (ms): 64.897 2026-03-31 16:38:17.967 | NQM26-CME[M] Daily #2 | Data Delay (ms): 78.977 2026-03-31 16:38:19.186 | ESM26-CME[M] Daily #1 | Data Delay (ms): 64.897 2026-03-31 16:38:19.186 | NQM26-CME[M] Daily #2 | Data Delay (ms): 78.977 2026-03-31 16:38:20.405 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.274 2026-03-31 16:38:20.405 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.117 2026-03-31 16:38:26.499 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.059 2026-03-31 16:38:26.500 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.104 2026-03-31 16:38:27.718 | ESM26-CME[M] Daily #1 | Data Delay (ms): 55.774 2026-03-31 16:38:27.719 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.104 2026-03-31 16:38:28.937 | ESM26-CME[M] Daily #1 | Data Delay (ms): 55.774 2026-03-31 16:38:28.938 | NQM26-CME[M] Daily #2 | Data Delay (ms): 56.826 2026-03-31 16:38:30.156 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.54 2026-03-31 16:38:30.157 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.649 2026-03-31 16:38:31.375 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.54 2026-03-31 16:38:31.376 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.649 2026-03-31 16:38:32.594 | NQM26-CME[M] Daily #2 | Data Delay (ms): 74.928 2026-03-31 16:38:33.813 | ESM26-CME[M] Daily #1 | Data Delay (ms): 77.424 2026-03-31 16:38:33.814 | NQM26-CME[M] Daily #2 | Data Delay (ms): 74.928 2026-03-31 16:38:35.032 | ESM26-CME[M] Daily #1 | Data Delay (ms): 77.424 2026-03-31 16:38:38.689 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.824 2026-03-31 16:38:38.689 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.68 2026-03-31 16:38:44.783 | NQM26-CME[M] Daily #2 | Data Delay (ms): 56.501 2026-03-31 16:38:47.221 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.323 2026-03-31 16:38:50.862 | NQM26-CME[M] Daily #2 | Data Delay (ms): 55.488 2026-03-31 16:38:53.301 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.305 2026-03-31 16:38:54.519 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.52 2026-03-31 16:38:54.519 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.305 2026-03-31 16:38:55.737 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.52 2026-03-31 16:38:59.395 | NQM26-CME[M] Daily #2 | Data Delay (ms): 53.41 2026-03-31 16:39:01.832 | NQM26-CME[M] Daily #2 | Data Delay (ms): 78.719 2026-03-31 16:39:03.051 | NQM26-CME[M] Daily #2 | Data Delay (ms): 53.863 2026-03-31 16:39:06.708 | ESM26-CME[M] Daily #1 | Data Delay (ms): 56.091 2026-03-31 16:39:07.927 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.684 2026-03-31 16:39:09.146 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.908 2026-03-31 16:39:09.146 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.684 2026-03-31 16:39:10.364 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.908 2026-03-31 16:39:10.365 | NQM26-CME[M] Daily #2 | Data Delay (ms): 51.51 2026-03-31 16:39:12.802 | ESM26-CME[M] Daily #1 | Data Delay (ms): 78.395 2026-03-31 16:39:16.460 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.227 2026-03-31 16:39:17.678 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.028 2026-03-31 16:39:20.116 | NQM26-CME[M] Daily #2 | Data Delay (ms): 53.139 2026-03-31 16:39:21.335 | ESM26-CME[M] Daily #1 | Data Delay (ms): 67.595 2026-03-31 16:39:21.335 | NQM26-CME[M] Daily #2 | Data Delay (ms): 53.139 2026-03-31 16:39:22.553 | ESM26-CME[M] Daily #1 | Data Delay (ms): 67.595 2026-03-31 16:39:23.773 | ESM26-CME[M] Daily #1 | Data Delay (ms): 55.202 2026-03-31 16:39:23.774 | NQM26-CME[M] Daily #2 | Data Delay (ms): 56.311 2026-03-31 16:39:24.991 | ESM26-CME[M] Daily #1 | Data Delay (ms): 55.202 2026-03-31 16:39:24.992 | NQM26-CME[M] Daily #2 | Data Delay (ms): 56.311 2026-03-31 16:39:26.210 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.989 2026-03-31 16:39:26.211 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.221 2026-03-31 16:39:29.867 | ESM26-CME[M] Daily #1 | Data Delay (ms): 78.604 2026-03-31 16:39:29.867 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.735 2026-03-31 16:39:31.086 | ESM26-CME[M] Daily #1 | Data Delay (ms): 78.604 2026-03-31 16:39:31.086 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.735 2026-03-31 16:39:33.524 | ESM26-CME[M] Daily #1 | Data Delay (ms): 74.051 2026-03-31 16:39:38.399 | ESM26-CME[M] Daily #1 | Data Delay (ms): 74.08 2026-03-31 16:39:39.618 | ESM26-CME[M] Daily #1 | Data Delay (ms): 76.119 2026-03-31 16:39:40.838 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.223 2026-03-31 16:39:44.494 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.483 2026-03-31 16:39:46.932 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.552 2026-03-31 16:39:46.932 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.259 2026-03-31 16:39:48.151 | ESM26-CME[M] Daily #1 | Data Delay (ms): 52.155 2026-03-31 16:39:48.151 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.259 2026-03-31 16:39:49.369 | ESM26-CME[M] Daily #1 | Data Delay (ms): 52.155 2026-03-31 16:39:49.370 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.056 2026-03-31 16:39:50.588 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.709 2026-03-31 16:39:50.589 | NQM26-CME[M] Daily #2 | Data Delay (ms): 54.793 2026-03-31 16:39:51.808 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.709 2026-03-31 16:39:51.808 | NQM26-CME[M] Daily #2 | Data Delay (ms): 54.793 2026-03-31 16:39:53.026 | ESM26-CME[M] Daily #1 | Data Delay (ms): 65.062 2026-03-31 16:39:53.026 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.95 2026-03-31 16:39:56.683 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.307 2026-03-31 16:39:56.684 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.841 2026-03-31 16:39:57.902 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.307 2026-03-31 16:39:57.902 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.841 2026-03-31 16:39:59.121 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.085 2026-03-31 16:39:59.121 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.638 2026-03-31 16:40:00.340 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.928 2026-03-31 16:40:00.340 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.638 2026-03-31 16:40:01.559 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.928 2026-03-31 16:40:01.559 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.515 2026-03-31 16:40:02.778 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.714 2026-03-31 16:40:02.779 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.32 2026-03-31 16:40:03.996 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.714 2026-03-31 16:40:03.997 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.32 2026-03-31 16:40:05.216 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.633 2026-03-31 16:40:05.216 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.053 2026-03-31 16:40:06.434 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.218 2026-03-31 16:40:06.435 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.053 2026-03-31 16:40:07.653 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.218 2026-03-31 16:40:07.654 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.965 2026-03-31 16:40:08.872 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.025 2026-03-31 16:40:08.873 | NQM26-CME[M] Daily #2 | Data Delay (ms): 63.014 2026-03-31 16:40:10.091 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.025 2026-03-31 16:40:10.091 | NQM26-CME[M] Daily #2 | Data Delay (ms): 63.014 2026-03-31 16:40:11.311 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.35 2026-03-31 16:40:13.748 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.54 2026-03-31 16:40:13.748 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.111 2026-03-31 16:40:14.967 | ESM26-CME[M] Daily #1 | Data Delay (ms): 56.282 2026-03-31 16:40:14.967 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.111 2026-03-31 16:40:16.186 | ESM26-CME[M] Daily #1 | Data Delay (ms): 56.282 2026-03-31 16:40:16.186 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.904 2026-03-31 16:40:17.405 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.103 2026-03-31 16:40:17.405 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.643 2026-03-31 16:40:18.623 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.103 2026-03-31 16:40:18.624 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.643 2026-03-31 16:40:19.842 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.811 2026-03-31 16:40:19.843 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.526 2026-03-31 16:40:21.061 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.755 2026-03-31 16:40:21.062 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.526 2026-03-31 16:40:22.280 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.755 2026-03-31 16:40:22.280 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.189 2026-03-31 16:40:23.499 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.491 2026-03-31 16:40:23.499 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.171 2026-03-31 16:40:24.718 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.491 2026-03-31 16:40:24.718 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.171 2026-03-31 16:40:25.937 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.139 2026-03-31 16:40:25.937 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.703 2026-03-31 16:40:27.156 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.953 2026-03-31 16:40:27.156 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.703 2026-03-31 16:40:28.375 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.953 2026-03-31 16:40:28.375 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.496 2026-03-31 16:40:29.593 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.65 2026-03-31 16:40:29.594 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.215 2026-03-31 16:40:30.813 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.65 2026-03-31 16:40:30.813 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.215 2026-03-31 16:40:32.031 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.452 2026-03-31 16:40:32.032 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.065 2026-03-31 16:40:33.251 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.353 2026-03-31 16:40:33.252 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.065 2026-03-31 16:40:34.470 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.353 2026-03-31 16:40:34.471 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.872 2026-03-31 16:40:35.689 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.134 2026-03-31 16:40:35.690 | NQM26-CME[M] Daily #2 | Data Delay (ms): 50.718 2026-03-31 16:40:36.908 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.134 2026-03-31 16:40:36.909 | NQM26-CME[M] Daily #2 | Data Delay (ms): 50.718 2026-03-31 16:40:38.127 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.062 2026-03-31 16:40:38.127 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.465 2026-03-31 16:40:39.346 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.062 2026-03-31 16:40:39.346 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.465 2026-03-31 16:40:40.565 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.654 2026-03-31 16:40:40.565 | NQM26-CME[M] Daily #2 | Data Delay (ms): 55.332 2026-03-31 16:40:41.784 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.404 2026-03-31 16:40:41.785 | NQM26-CME[M] Daily #2 | Data Delay (ms): 55.332 2026-03-31 16:40:43.003 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.404 2026-03-31 16:40:43.003 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.976 2026-03-31 16:40:44.222 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.176 2026-03-31 16:40:44.222 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.784 2026-03-31 16:40:45.441 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.176 2026-03-31 16:40:45.441 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.784 2026-03-31 16:40:46.659 | ESM26-CME[M] Daily #1 | Data Delay (ms): 59.949 2026-03-31 16:40:46.660 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.506 2026-03-31 16:40:47.878 | ESM26-CME[M] Daily #1 | Data Delay (ms): 52.744 2026-03-31 16:40:47.880 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.506 2026-03-31 16:40:49.097 | ESM26-CME[M] Daily #1 | Data Delay (ms): 52.744 2026-03-31 16:40:50.301 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.512 2026-03-31 16:40:50.301 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.121 2026-03-31 16:40:51.520 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.512 2026-03-31 16:40:51.520 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.121 2026-03-31 16:40:52.739 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.821 2026-03-31 16:40:58.833 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.068 2026-03-31 16:40:58.833 | NQM26-CME[M] Daily #2 | Data Delay (ms): 53.639 2026-03-31 16:41:00.052 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.307 2026-03-31 16:41:00.052 | NQM26-CME[M] Daily #2 | Data Delay (ms): 53.639 2026-03-31 16:41:01.271 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.307 2026-03-31 16:41:01.271 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.397 2026-03-31 16:41:02.490 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.744 2026-03-31 16:41:02.490 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.241 2026-03-31 16:41:03.709 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.744 2026-03-31 16:41:03.709 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.241 2026-03-31 16:41:04.927 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.409 2026-03-31 16:41:04.928 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.069 2026-03-31 16:41:06.146 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.129 2026-03-31 16:41:06.147 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.069 2026-03-31 16:41:07.365 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.129 2026-03-31 16:41:07.366 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.749 2026-03-31 16:41:08.584 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.926 2026-03-31 16:41:08.585 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.749 2026-03-31 16:41:09.803 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.926 2026-03-31 16:41:09.804 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.516 2026-03-31 16:41:11.022 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.695 2026-03-31 16:41:11.023 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.246 2026-03-31 16:41:12.241 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.695 2026-03-31 16:41:12.241 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.246 2026-03-31 16:41:13.460 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.52 2026-03-31 16:41:13.460 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.049 2026-03-31 16:41:14.679 | ESM26-CME[M] Daily #1 | Data Delay (ms): 59.223 2026-03-31 16:41:14.679 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.049 2026-03-31 16:41:15.898 | ESM26-CME[M] Daily #1 | Data Delay (ms): 59.223 2026-03-31 16:41:15.898 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.89 2026-03-31 16:41:17.116 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.997 2026-03-31 16:41:17.117 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.522 2026-03-31 16:41:18.335 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.997 2026-03-31 16:41:18.336 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.522 2026-03-31 16:41:19.555 | ESM26-CME[M] Daily #1 | Data Delay (ms): 55.729 2026-03-31 16:41:19.556 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.904 2026-03-31 16:41:20.774 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.531 2026-03-31 16:41:20.775 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.904 2026-03-31 16:41:21.992 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.531 2026-03-31 16:41:23.211 | ESM26-CME[M] Daily #1 | Data Delay (ms): 59.336 2026-03-31 16:41:23.212 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.091 2026-03-31 16:41:24.430 | ESM26-CME[M] Daily #1 | Data Delay (ms): 59.336 2026-03-31 16:41:24.430 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.091 2026-03-31 16:41:25.649 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.043 2026-03-31 16:41:25.649 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.728 2026-03-31 16:41:26.868 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.84 2026-03-31 16:41:26.869 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.728 2026-03-31 16:41:28.087 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.84 2026-03-31 16:41:28.087 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.38 2026-03-31 16:41:29.306 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.566 2026-03-31 16:41:29.307 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.216 2026-03-31 16:41:30.524 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.566 2026-03-31 16:41:30.525 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.216 2026-03-31 16:41:31.743 | ESM26-CME[M] Daily #1 | Data Delay (ms): 50.364 2026-03-31 16:41:31.744 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.884 2026-03-31 16:41:32.962 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.225 2026-03-31 16:41:32.963 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.884 2026-03-31 16:41:34.181 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.225 2026-03-31 16:41:34.182 | NQM26-CME[M] Daily #2 | Data Delay (ms): 55.698 2026-03-31 16:41:35.400 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.932 2026-03-31 16:41:35.401 | NQM26-CME[M] Daily #2 | Data Delay (ms): 55.698 2026-03-31 16:41:36.619 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.932 2026-03-31 16:41:36.620 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.537 2026-03-31 16:41:37.838 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.646 2026-03-31 16:41:37.838 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.209 2026-03-31 16:41:39.057 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.646 2026-03-31 16:41:39.057 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.209 2026-03-31 16:41:40.276 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.518 2026-03-31 16:41:40.277 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.998 2026-03-31 16:41:41.495 | ESM26-CME[M] Daily #1 | Data Delay (ms): 54.168 2026-03-31 16:41:41.495 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.998 2026-03-31 16:41:42.714 | ESM26-CME[M] Daily #1 | Data Delay (ms): 54.168 2026-03-31 16:41:42.715 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.758 2026-03-31 16:41:43.932 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.055 2026-03-31 16:41:43.933 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.503 2026-03-31 16:41:45.151 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.055 2026-03-31 16:41:45.152 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.503 2026-03-31 16:41:46.370 | ESM26-CME[M] Daily #1 | Data Delay (ms): 56.824 2026-03-31 16:41:46.371 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.932 2026-03-31 16:41:47.589 | ESM26-CME[M] Daily #1 | Data Delay (ms): 53.477 2026-03-31 16:41:47.590 | NQM26-CME[M] Daily #2 | Data Delay (ms): 57.932 2026-03-31 16:41:48.808 | ESM26-CME[M] Daily #1 | Data Delay (ms): 53.477 2026-03-31 16:41:48.809 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.083 2026-03-31 16:41:50.027 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.273 2026-03-31 16:41:50.027 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.848 2026-03-31 16:41:51.246 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.273 2026-03-31 16:41:51.246 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.848 2026-03-31 16:41:52.465 | ESM26-CME[M] Daily #1 | Data Delay (ms): 54.992 2026-03-31 16:41:52.465 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.652 2026-03-31 16:41:53.684 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.882 2026-03-31 16:41:53.685 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.652 2026-03-31 16:41:54.903 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.882 2026-03-31 16:41:54.903 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.335 2026-03-31 16:41:56.122 | ESM26-CME[M] Daily #1 | Data Delay (ms): 57.538 2026-03-31 16:41:58.559 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.37 2026-03-31 16:41:58.560 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.923 2026-03-31 16:42:00.998 | NQM26-CME[M] Daily #2 | Data Delay (ms): 93.993 2026-03-31 16:42:02.216 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.914 2026-03-31 16:42:02.217 | NQM26-CME[M] Daily #2 | Data Delay (ms): 93.993 2026-03-31 16:42:03.435 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.914 2026-03-31 16:42:03.435 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.726 2026-03-31 16:42:04.654 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.404 2026-03-31 16:42:04.655 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.509 2026-03-31 16:42:05.873 | ESM26-CME[M] Daily #1 | Data Delay (ms): 60.404 2026-03-31 16:42:05.873 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.509 2026-03-31 16:42:07.092 | ESM26-CME[M] Daily #1 | Data Delay (ms): 51.338 2026-03-31 16:42:07.092 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.234 2026-03-31 16:42:08.311 | ESM26-CME[M] Daily #1 | Data Delay (ms): 53.932 2026-03-31 16:42:08.312 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.234 2026-03-31 16:42:09.530 | ESM26-CME[M] Daily #1 | Data Delay (ms): 53.932 2026-03-31 16:42:09.530 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.99 2026-03-31 16:42:10.748 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.805 2026-03-31 16:42:10.749 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.813 2026-03-31 16:42:11.967 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.805 2026-03-31 16:42:11.968 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.813 2026-03-31 16:42:13.186 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.481 2026-03-31 16:42:13.187 | NQM26-CME[M] Daily #2 | Data Delay (ms): 55.555 2026-03-31 16:42:14.405 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.256 2026-03-31 16:42:14.406 | NQM26-CME[M] Daily #2 | Data Delay (ms): 55.555 2026-03-31 16:42:15.624 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.256 2026-03-31 16:42:15.624 | NQM26-CME[M] Daily #2 | Data Delay (ms): 58.431 2026-03-31 16:42:16.843 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.082 2026-03-31 16:42:19.281 | ESM26-CME[M] Daily #1 | Data Delay (ms): 59.797 2026-03-31 16:42:19.281 | NQM26-CME[M] Daily #2 | Data Delay (ms): 56.807 2026-03-31 16:42:20.500 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.854 2026-03-31 16:42:20.500 | NQM26-CME[M] Daily #2 | Data Delay (ms): 56.807 2026-03-31 16:42:21.719 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.854 2026-03-31 16:42:21.719 | NQM26-CME[M] Daily #2 | Data Delay (ms): 61.671 2026-03-31 16:42:22.938 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.303 2026-03-31 16:42:22.938 | NQM26-CME[M] Daily #2 | Data Delay (ms): 53.36 2026-03-31 16:42:24.156 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.303 2026-03-31 16:42:24.157 | NQM26-CME[M] Daily #2 | Data Delay (ms): 53.36 2026-03-31 16:42:25.376 | ESM26-CME[M] Daily #1 | Data Delay (ms): 59.092 2026-03-31 16:42:25.377 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.279 2026-03-31 16:42:26.594 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.988 2026-03-31 16:42:26.595 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.279 2026-03-31 16:42:27.813 | ESM26-CME[M] Daily #1 | Data Delay (ms): 61.988 2026-03-31 16:42:27.814 | NQM26-CME[M] Daily #2 | Data Delay (ms): 54.901 2026-03-31 16:42:29.033 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.624 2026-03-31 16:42:29.033 | NQM26-CME[M] Daily #2 | Data Delay (ms): 54.901 2026-03-31 16:42:30.251 | ESM26-CME[M] Daily #1 | Data Delay (ms): 62.624 2026-03-31 16:42:30.252 | NQM26-CME[M] Daily #2 | Data Delay (ms): 62.729 2026-03-31 16:42:31.470 | NQM26-CME[M] Daily #2 | Data Delay (ms): 60.443 2026-03-31 16:42:33.905 | ESM26-CME[M] Daily #1 | Data Delay (ms): 59.115 2026-03-31 16:42:33.905 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.206 2026-03-31 16:42:35.124 | ESM26-CME[M] Daily #1 | Data Delay (ms): 58.841 2026-03-31 16:42:35.124 | NQM26-CME[M] Daily #2 | Data Delay (ms): 59.206 For an understanding, of how that data delay is calculated, refer to: Prices / Data Falling Behind: 4.20 - Precise Measurement of Delay Compared to Exchange Time Stamping What we need from you is to enable heartbeat logging and then we need the heartbeat messages at the time this is occurring: Prices / Data Falling Behind: 4.17 - Providing Heartbeat Messages to Sierra Chart Support 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-04-01 14:37:59
|
| [2026-04-01 14:40:02] |
| Sierra_Chart Engineering - Posts: 23657 |
|
We can assure you, it is due to Internet connectivity: I can assure it's definitely not an internet issue as I'm always monitoring it. It may be, somewhere else including with carriers that we use, but it is Internet connectivity! We have explained this time and time and time again. Refer to: Prices / Data Falling Behind: 4.21 - Why a Data Feed Stops or Becomes Delayed We will never ever deviate from this basic fact. This is definitively due to Internet connectivity! This is absolute definitive fact. 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-04-01 19:32:15] |
| Sierra_Chart Engineering - Posts: 23657 |
|
One thing that occurred to us, is the new server we set up ds7,ds7-2 we may not have optimized the network adapter settings on the server. We are going to be checking on that. Therefore, this can result in packet loss, which would cause the data feed to stop. We did notice a lag today of 1.5 seconds when using that server, at the time (US Eastern) shown below: 2026-04-01 14:01:04.444 | Denali Data Feed | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=2, NumberOfOutstandingSendBuffers=7, TransmissionDelayInMilliseconds=195, ServerSendBufferSizeInBytes=14147, ActualMessageDelay=1.5 seconds, DataCompRatio=3.18, UncompressedBytes=566314719, CompressionTime=6.661027(secs), NumCompressions=814473, Source=10.10.20.253, MaxSendBufferSize=40905, MaxSendBufferSizeDateTime=2026-04-01 18:00:00 We will work on the optimization this evening and that may very well be the reason for the problem. We need to see the heartbeat messages when you have a problem so we can better isolate what is happening and where. One additional thing we could add to the heartbeat messages is any input delay into the real-time server process. If there is no reported input delay, then we know the connectivity is good from the source. One thing we want to reiterate, is that the original problem at the beginning of this thread is definitively resolved. 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-04-01 19:43:14
|
| [2026-04-01 20:38:04] |
| Rui S - Posts: 234 |
|
Thank you for analyzing this issue. One thing that occurred to us, is the new server we set up ds7,ds7-2 we may not have optimized the network adapter settings on the server.
I wasn't using any of those servers, I was connected to DS26 and ds32-2. I will try ds7 and ds7-2 tomorrow though. We need to see the heartbeat messages when you have a problem so we can better isolate what is happening and where.
I'll get it next time it happens, although I would rather it wouldn't happen again :) One thing we want to reiterate, is that the original problem at the beginning of this thread is definitively resolved.
I'm pretty convinced you are correct here, yes. This issue seems different somehow. In any case, as I've stated in the past, I know for sure when there is any internet problem between Denali servers and my computer and I also know exactly where it happened, because I have a software running full time while I'm trading that tracks the entire route and servers in between. Please see the file attached. As you said, most of the problems happen because of the internet connection, whether it is from your ISP, my ISP or the route in between. Recently I alerted you of an issue with you ISP, which was resolved a few hours later. That day, they even changed the usual route. However, these "normal" events haven't been the case I described today. There really were several interruptions and stuttering due to the bursts of volume, but the connection between my PC and your servers was always absolutely normal. That's why I thought the problem could be from CME servers or the connection between CME servers and Denali servers. Anyway, I want you to know that I dislike this as much as you do and I really hate to have to bother you with such problems. However, after having to close a position blindly yesterday due to those freezes, I got seriously concerned. Also, if users don't let you know about problems, you might not know at all. Whatever the problem is, I wish you can find it. Thank you. |
Private File |
| [2026-04-02 00:57:36] |
| Sierra_Chart Engineering - Posts: 23657 |
|
We really should not have said this because this is extremely unlikely to cause packet loss thinking about this some more: One thing that occurred to us, is the new server we set up ds7,ds7-2 we may not have optimized the network adapter settings on the server. We are going to be checking on that. Therefore, this can result in packet loss, which would cause the data feed to stop.
Default network adapter configurations are not so bad to be causing packet loss.Nevertheless some changes have been made. Most of the settings were already optimal but some additional changes were made. 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-04-02 00:58:31
|
| [2026-04-02 14:52:30] |
| Rui S - Posts: 234 |
|
Hello Support. Today there was a much less significant issue than the previous days, but I hope it gives you a lead on what's going on. Today internet connection between Denali Servers and my PC has been perfect all the time up to this moment. (See file attached) Here you have the log below. 2026-04-02 15:35:47.792 | Teton CME Routing | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=4, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=0, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=0.00, UncompressedBytes=338135, CompressionTime=0.000000(secs), NumCompressions=0, Source=216.200.108.154 2026-04-02 15:35:51.028 | Denali Data Feed | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=4, NumberOfOutstandingSendBuffers=1, TransmissionDelayInMilliseconds=20, ServerSendBufferSizeInBytes=6748, ActualMessageDelay=-0.1 seconds, DataCompRatio=3.44, UncompressedBytes=496537259, CompressionTime=2.610380(secs), NumCompressions=160508, Source=10.10.20.72, MaxSendBufferSize=92918, MaxSendBufferSizeDateTime=2026-04-02 14:16:29 2026-04-02 15:35:57.782 | Teton CME Routing | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=14, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=0, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=0.00, UncompressedBytes=338238, CompressionTime=0.000000(secs), NumCompressions=0, Source=216.200.108.154 2026-04-02 15:36:06.776 | Denali Data Feed (Market Orders Data) | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=18, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=20, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=1.03, UncompressedBytes=53945, CompressionTime=0.006315(secs), NumCompressions=728, Source=10.10.20.72, MaxSendBufferSize=235, MaxSendBufferSizeDateTime=2026-04-02 10:34:58 2026-04-02 15:36:07.784 | Teton CME Routing | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=3, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=0, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=0.00, UncompressedBytes=338341, CompressionTime=0.000000(secs), NumCompressions=0, Source=216.200.108.154 2026-04-02 15:36:11.715 | Denali Data Feed | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=2, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=20, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=3.45, UncompressedBytes=502450751, CompressionTime=2.623410(secs), NumCompressions=160592, Source=10.10.20.72, MaxSendBufferSize=473748, MaxSendBufferSizeDateTime=2026-04-02 14:36:05 2026-04-02 15:36:17.798 | Teton CME Routing | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=13, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=0, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=0.00, UncompressedBytes=338444, CompressionTime=0.000000(secs), NumCompressions=0, Source=216.200.108.154 2026-04-02 15:36:26.780 | Denali Data Feed (Market Orders Data) | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=18, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=20, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=1.03, UncompressedBytes=54019, CompressionTime=0.006321(secs), NumCompressions=729, Source=10.10.20.72, MaxSendBufferSize=235, MaxSendBufferSizeDateTime=2026-04-02 10:34:58 2026-04-02 15:36:27.787 | Teton CME Routing | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=3, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=0, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=0.00, UncompressedBytes=338547, CompressionTime=0.000000(secs), NumCompressions=0, Source=216.200.108.154 2026-04-02 15:36:31.226 | Denali Data Feed | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=3, NumberOfOutstandingSendBuffers=2, TransmissionDelayInMilliseconds=20, ServerSendBufferSizeInBytes=17035, ActualMessageDelay=-0.1 seconds, DataCompRatio=3.45, UncompressedBytes=509035786, CompressionTime=2.638917(secs), NumCompressions=160850, Source=10.10.20.72, MaxSendBufferSize=473748, MaxSendBufferSizeDateTime=2026-04-02 14:36:05 2026-04-02 15:36:37.788 | Teton CME Routing | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=13, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=0, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=0.00, UncompressedBytes=338650, CompressionTime=0.000000(secs), NumCompressions=0, Source=216.200.108.154 2026-04-02 15:36:46.784 | Denali Data Feed (Market Orders Data) | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=18, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=20, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=1.03, UncompressedBytes=54093, CompressionTime=0.006328(secs), NumCompressions=730, Source=10.10.20.72, MaxSendBufferSize=235, MaxSendBufferSizeDateTime=2026-04-02 10:34:58 2026-04-02 15:36:47.790 | Teton CME Routing | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=3, NumberOfOutstandingSendBuffers=0, TransmissionDelayInMilliseconds=0, ServerSendBufferSizeInBytes=0, ActualMessageDelay=-0.1 seconds, DataCompRatio=0.00, UncompressedBytes=338753, CompressionTime=0.000000(secs), NumCompressions=0, Source=216.200.108.154 Date Time Of Last Edit: 2026-04-02 15:01:35
|
Private File |
| [2026-04-02 19:37:22] |
| gz6969 - Posts: 51 |
|
@Rui: where are you located? I'm in Austria Europe and Sierra is freezing very often since yesterday. Never had this in this intensity before. When it freezes I also cannot reach the Sierra Chart website(even on my iPhone and I did not use my WLAN for testing). No problem calling other websites at the same time. I see very often ping timeouts. Here at thursday 21:34 in my time for example: Antwort von 64.152.155.17: Bytes=32 Zeit=121ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=120ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=121ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=118ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=124ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=121ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=121ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=123ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=122ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=120ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=121ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=122ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=122ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=120ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=118ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=119ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=121ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=124ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=119ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=123ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=120ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=123ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=122ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=120ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=118ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=121ms TTL=56 Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Antwort von 64.152.155.17: Bytes=32 Zeit=129ms TTL=56 Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Antwort von 64.152.155.17: Bytes=32 Zeit=128ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=128ms TTL=56 Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Antwort von 64.152.155.17: Bytes=32 Zeit=120ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=122ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=123ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=121ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=126ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=122ms TTL=56 Antwort von 64.152.155.17: Bytes=32 Zeit=125ms TTL=56 Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. Zeitüberschreitung der Anforderung. C:\>tracert 64.152.155.17 Routenverfolgung zu 64.152.155.17 über maximal 30 Hops 1 2 ms 2 ms 2 ms telekom.ip [192.168.0.1] 2 11 ms 10 ms 13 ms at-vie09c-rt01.as8412.net [217.25.120.3] 3 48 ms 10 ms 10 ms at-vie09c-rc01.as8412.net [217.25.122.250] 4 12 ms 10 ms 22 ms 62.157.248.249 5 10 ms 11 ms 10 ms vie-sb5-i.VIE.AT.NET.DTAG.DE [217.239.40.153] 6 12 ms 9 ms 10 ms 62.159.61.127 7 126 ms 134 ms 125 ms ae8.8.bar3.Detroit1.net.lumen.tech [4.69.143.253] 8 122 ms 122 ms 124 ms 64.152.155.17 Ablaufverfolgung beendet. C:\>tracert 69.39.70.241 Routenverfolgung zu 69.39.70.241 über maximal 30 Hops 1 2 ms 1 ms 1 ms telekom.ip [192.168.0.1] 2 10 ms 9 ms 12 ms at-vie09c-rt01.as8412.net [217.25.120.3] 3 18 ms 17 ms 9 ms at-vie09c-rc01.as8412.net [217.25.122.250] 4 11 ms 10 ms 10 ms 62.157.248.249 5 11 ms 15 ms 11 ms 80.156.162.179 6 10 ms 10 ms 9 ms win-bb2-link.ip.twelve99.net [62.115.114.182] 7 21 ms 21 ms 20 ms ffm-bb2-link.ip.twelve99.net [62.115.138.22] 8 29 ms 30 ms 29 ms prs-bb2-link.ip.twelve99.net [62.115.122.138] 9 35 ms 34 ms 35 ms ldn-bb2-link.ip.twelve99.net [62.115.133.238] 10 * * * Zeitüberschreitung der Anforderung. 11 132 ms 132 ms 140 ms det-b3-link.ip.twelve99.net [62.115.137.149] 12 140 ms 139 ms 139 ms 123net-ic-349731.ip.twelve99-cust.net [62.115.180.114] 13 130 ms 129 ms 128 ms 67.214.125.193 14 126 ms 124 ms 126 ms 69.39.70.241 Ablaufverfolgung beendet. Date Time Of Last Edit: 2026-04-02 19:48:40
|
| [2026-04-02 20:10:45] |
| Rui S - Posts: 234 |
|
Hi gz6969, I'm located in Portugal. I'm in Austria Europe and Sierra is freezing very often since yesterday. Never had this in this intensity before. When it freezes I also cannot reach the Sierra Chart website(even on my iPhone and I did not use my WLAN for testing).
What you describe sounds like an internet problem, something not well in the route from Chicago. For me Denali data feed is not having any other problems than the momentarily ones that I've described above and just upon heavy volume bursts. Try to use a directed server. For your location the server located in Germany - DS14-2.sierracharts.com - might work well. |
| [2026-04-02 22:44:02] |
| Sierra_Chart Engineering - Posts: 23657 |
|
Yes post #94, is an Internet connectivity issue. Regarding post #93, what is the issue you had at the time of those messages? There is no indication of any problem at all. If the data feed is stopping for you, it is certainly not a problem at the server side. This is very clear. 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-04-03 08:34:07] |
| gz6969 - Posts: 51 |
|
Everytime I had these timeouts Sierra was freezing and also the Sierra Website was not available. My internet connection was available and had no problems at the times Sierra was not working. Because the Sierra website was also not reachable from my iPhone at the same time it must be a internet problem(the iPhone was not using the same internet connection as my pc at the time of these freezes) @Rui: thanks! I will try the server DS14-2.sierracharts.com. I assume it's this setting: Sierra Chart Server Settings: CME Exchange Data Feed Server Address and Port Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) Date Time Of Last Edit: 2026-04-03 08:39:06
|
| [2026-04-03 10:34:21] |
| Rui S - Posts: 234 |
|
Regarding post #93, what is the issue you had at the time of those messages? There is no indication of any problem at all. If the data feed is stopping for you, it is certainly not a problem at the server side. This is very clear.
Thank you for analyzing the log. The problem was that during about one minute there was some very short time freezings, probably not enough for the log to show them. But as I said the day's before episodes were much worse. I will keep the heartbeat messages on and if it happens again I'll try to catch it. What should I look for in the heartbeat messages when an issue like this happens? I'm asking because it will be pointless to post it here if it doesn't show any problem. Thank you. |
| [2026-04-03 10:35:38] |
| Rui S - Posts: 234 |
|
@Rui: thanks! I will try the server DS14-2.sierracharts.com. I assume it's this setting:
Yes, that's correct. |
| [2026-04-03 17:03:11] |
| gz6969 - Posts: 51 |
|
Is there also a server in Germany for the historical CME data -> "CME Exchange Data Feed Historical Server Address Override"?
|
To post a message in this thread, you need to log in with your Sierra Chart account: