Support Board
Date/Time: Sun, 24 Nov 2024 16:55:17 +0000
poor connection
View Count: 309
| [2024-05-20 22:55:22] |
| User247682 - Posts: 7 |
|
Why my connection is so poor when I went overseas. I have like 1 reconnection every 60sec with error like: - Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. - Socket gracefully closed by remote side. It is same laptop that I trade in home so no problem with firewall, also my present 5G speed test is like 395mb/s so everything is working like a charm, but not sierrachart. Connection is so poor that I have to wait like 5min to let SC download data first for 3 charts. Sometimes its faster or even no reconnection, but I can see clearly there is a problem with overloading server? Anybody have the same problem with denali? |
| [2024-05-21 14:42:31] |
| John - SC Support - Posts: 36238 |
|
For information on the Windows Error Code 10053, refer to the following: Data/Trading Service Connection and Symbol Issues: 1.2. Network Communication or Server Problem For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-05-22 11:27:12] |
| User512353 - Posts: 42 |
|
I have the same problem here, intermittently showing up since May 6 (not every day). My observations during RTH: - Charts suddenly stop updating, but this typically effects NOT all the symbols in a chartbook. So, other symbol's charts keep updating. This indicates that there is no network error, but hints to a server CPU capacity problem. - The problem typically occurs when there is a large number of transactions for the symbol at the exchange, e.g. for ESM4. This also hints to a server CPU capacity problem. - A concurrent ping to ds12.sierracharts.com (38.103.112.181), which is one of the involved data servers that reconnects, reports a whopping 30% packet loss during RTH. This is not only during the time that charts freeze, but a common observation during RTH. This again hints to a server CPU capacity problem, because the round trip times are pretty constant and not different from ETH. (There is no packet loss during ETH.) Do you monitor the data server CPU capacity? Do you monitor connection losses / reconnects of the data servers? I strongly suggest to review the data server behavior. If there is no CPU capacity shortage, you should look for contention in the software stack. That's all I can currently say from here with my 30 years IT experience in server hardware, firmware, OS, and software R&D. The problem should be looked at, because these problems seriously affect trading. It would also be desirable to have more debugging aids at hand for these problems. These should be built into the SC software. A standalone debugging tool may also be helpful to cut off SC software problems. Plus some kind of dashboard for the server status, e.g. like IBKR implements in TWS. |
| [2024-05-23 23:24:27] |
| Sierra_Chart Engineering - Posts: 17156 |
|
There is no problem at all with our servers or server load. We know that 100%. The server load, typically does not exceed 5% of capacity. This is strictly an Internet connectivity issue, over in Europe. That is where the packet loss is occurring. - A concurrent ping to ds12.sierracharts.com (38.103.112.181), which is one of the involved data servers that reconnects, reports a whopping 30% packet loss during RTH. This is not only during the time that charts freeze, but a common observation during RTH. This again hints to a server CPU capacity problem, because the round trip times are pretty constant and not different from ETH. (There is no packet loss during ETH.) And it is not a server which is even responding to pings. The ping is responded to by high-performance network switches which never operate even close to capacity. We are aware of this kind of packet loss issue and we know it is a peering issue, with our primary ISP Cogent, occurring in Europe. It may not be with Cogent themselves, but with who they peer with. We are working, over the next two weeks, adding another ISP, to address issues like this. 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-24 06:17:01
|
| [2024-05-24 13:39:02] |
| Sierra_Chart Engineering - Posts: 17156 |
|
Here is some monitoring we did before the open today and leading into the 9:30 AM US Eastern time open for several minutes by pinging one of the servers from the United States: Reply from 38.103.112.181: bytes=1 time=9ms TTL=55
Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=11ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=8ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=8ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=8ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=8ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=8ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=11ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=8ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Request timed out. Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=10ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Reply from 38.103.112.181: bytes=1 time=9ms TTL=55 Ping statistics for 38.103.112.181: Packets: Sent = 2656, Received = 2639, Lost = 17 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 12ms, Average = 9ms So you can see the loss is extremely minimal effectively working out to 0%. 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-24 16:37:20] |
| User247682 - Posts: 7 |
|
this is my: Pinging 38.103.112.181 with 32 bytes of data: Reply from 38.103.112.181: bytes=32 time=215ms TTL=50 Reply from 38.103.112.181: bytes=32 time=206ms TTL=50 Reply from 38.103.112.181: bytes=32 time=199ms TTL=50 Ping statistics for 38.103.112.181: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 199ms, Maximum = 215ms, Average = 208ms after 2pm US it is even worst than here. edit just from 10min ago: Pinging 38.103.112.181 with 32 bytes of data: Request timed out. Request timed out. Reply from 38.103.112.181: bytes=32 time=283ms TTL=50 Reply from 38.103.112.181: bytes=32 time=303ms TTL=50 Ping statistics for 38.103.112.181: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 283ms, Maximum = 303ms, Average = 293ms Date Time Of Last Edit: 2024-05-24 20:09:44
|
| [2024-05-24 16:39:53] |
| Sierra_Chart Engineering - Posts: 17156 |
|
The new ISP, should be online in about in about 12 to 14 days. We are also going to contact Cogent and give them your IP address.
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-24 16:40:52
|
| [2024-05-24 16:47:37] |
| User247682 - Posts: 7 |
|
my ip is dynamic because of mobile router, so no need to send my ip.
|
| [2024-05-24 16:59:38] |
| nosast - Posts: 312 |
|
This is 99% a peering issue with Cogent. I experience the same from Europe and can't wait for the new ISP to be online. Hoping that Cogents backbone routers are not in the trace then anymore. During Europe evenings this is really bad - during the day it's working ok.
Date Time Of Last Edit: 2024-05-24 20:57:56
|
| [2024-05-24 17:07:31] |
| User247682 - Posts: 7 |
|
yes, I am from Europe too, and I stop trading at evening.
|
| [2024-05-24 22:40:43] |
| User512353 - Posts: 42 |
|
This is my traceroute to 38.103.112.183 (first two entries deleted to hide my IP address - it is dynamic anyway) traceroute to 38.103.112.183 (38.103.112.183), 30 hops max, 60 byte packets 1 2 3 c-ge1-2.osr0-krisztina.net.telekom.hu (81.183.246.63) 5.083 ms tge0-1-0-2.er1-szeged.net.telekom.hu (84.1.80.6) 7.512 ms 81.183.246.61 (81.183.246.61) 7.446 ms 4 81.183.0.37 (81.183.0.37) 4.891 ms 81.183.3.32 (81.183.3.32) 4.826 ms 81.183.3.6 (81.183.3.6) 4.763 ms 5 vie-sb5-i.VIE.AT.NET.DTAG.DE (217.239.40.153) 10.949 ms 80.157.206.178 (80.157.206.178) 10.888 ms vie-sb5-i.VIE.AT.NET.DTAG.DE (217.239.40.153) 10.826 ms 6 * vie-sb5-i.VIE.AT.NET.DTAG.DE (217.239.40.153) 10.572 ms * 7 be3462.ccr22.muc03.atlas.cogentco.com (154.54.59.182) 17.526 ms 17.455 ms * 8 be2960.ccr42.fra03.atlas.cogentco.com (154.54.36.253) 21.873 ms 21.840 ms 21.811 ms 9 be5160.ccr41.ams03.atlas.cogentco.com (130.117.3.66) 31.443 ms be2814.ccr42.ams03.atlas.cogentco.com (130.117.0.141) 29.414 ms be5160.ccr41.ams03.atlas.cogentco.com (130.117.3.66) 31.384 ms 10 be2182.ccr21.lpl01.atlas.cogentco.com (154.54.77.246) 131.951 ms be2399.ccr22.lpl01.atlas.cogentco.com (130.117.0.6) 200.151 ms be12488.ccr42.lon13.atlas.cogentco.com (130.117.51.41) 200.087 ms 11 be3042.ccr21.ymq01.atlas.cogentco.com (154.54.44.162) 200.048 ms be3488.ccr52.lhr01.atlas.cogentco.com (154.54.60.14) 200.008 ms be3043.ccr22.ymq01.atlas.cogentco.com (154.54.44.166) 199.964 ms 12 be4283.ccr32.bos01.atlas.cogentco.com (154.54.47.145) 199.925 ms be3393.ccr31.bos01.atlas.cogentco.com (154.54.47.141) 204.277 ms be3043.ccr22.ymq01.atlas.cogentco.com (154.54.44.166) 204.234 ms 13 be3600.ccr22.alb02.atlas.cogentco.com (154.54.0.221) 204.310 ms be2099.ccr31.bos01.atlas.cogentco.com (154.54.82.34) 204.190 ms be2994.ccr22.cle04.atlas.cogentco.com (154.54.31.233) 204.170 ms 14 be2993.ccr21.cle04.atlas.cogentco.com (154.54.31.225) 204.241 ms be2717.ccr41.ord01.atlas.cogentco.com (154.54.6.221) 204.121 ms be2718.ccr42.ord01.atlas.cogentco.com (154.54.7.129) 204.091 ms 15 be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 204.062 ms be2717.ccr41.ord01.atlas.cogentco.com (154.54.6.221) 204.040 ms be2765.ccr41.ord03.atlas.cogentco.com (154.54.45.18) 203.678 ms 16 be2051.agr61.ord03.atlas.cogentco.com (154.54.84.50) 203.554 ms 203.477 ms be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 203.383 ms 17 * be2051.agr61.ord03.atlas.cogentco.com (154.54.84.50) 203.164 ms 126.943 ms 18 * * * after 18 only * * *, so traceroute gets lost here. So, if I interpret the DNS names correctly, the routing is: Magyar Telekom: Budapest, (Szeged ?) -> Deutsche Telekom (Austria): Vienna -> Cogent: Munich, Frankfurt, Amsterdam, Liverpool, Montreal, Boston, Albany, Cleveland, Chicago I had no outages on the data stream yesterday (5/23) and today (5/24). I did not check the ping. Date Time Of Last Edit: 2024-05-24 22:59:50
|
| [2024-05-25 14:30:45] |
| Sierra_Chart Engineering - Posts: 17156 |
|
We expect to have the new ISP online by June 1. We will provide more information around that 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: