Support Board
Date/Time: Fri, 13 Jun 2025 13:42:05 +0000
[Sticky] [Locked] - Explanation NASDAQ TotalView Interruption 2025-06-11 (Wednesday)
View Count: 151
| [2025-06-12 08:36:27] |
| Sierra_Chart Engineering - Posts: 19909 |
|
There was an interruption of the NASDAQ TotalView data feed at approximately 12:30 PM US Eastern time June 11, 2025. The interruption was over an hour. Recently we have invested considerably in new network connections and hardware in order to provide, very reliable 100% uptime services for US equities and other data feeds, even including CME data. So this was a great disappointment and the core reason, was a failure of two different service providers. We do not expect such an incident again because this was a very unusual situation. At the time this happened, we had the following wide area network connections available to us: - 100 Gb wavelength connection to CH2 (provided by Cogent and fully operational) - 100 Gb wavelength connection to CH2 (provided by Crown Castle and was operational, but experienced an interruption) - 10 Gb connection to NY4 (was available, but not usable immediately because we were in transition, from the day before, from the to be discontinued 100 Gb Crown Castle connection to the new 100 Gb Cogent connection. So yesterday when this happened, we actually had two operational 100 Gb wavelength connections. The problem is that our service provider at CH2 in Chicago had a firewall configuration issue where we could not establish a TCP connection to the NASDAQ TotalView server over the 100 Gb Cogent connection. Therefore, when the Crown Castle connection experienced an interruption, and there was an automatic failover to the Cogent connection we could not establish a connection due to this firewall issue. This firewall issue was a failure from our service provider in CH2. They should of had this programmed correctly and they were told about what our requirements were previously. They later told us yesterday: "Acknowledged on the below – have found the issue with the TCP connections and have a change in to get this rectified. This will be pushed in overnight change window so I will reach out when this is good to test." This firewall issue, is an initial configuration issue, related to the the new 100 Gb Cogent connection to CH2. It will not occur again. So what has happened, is that the NY4 connection while it was available, it was not immediately usable because the network switch, that it was connected to, was being used by the new 100 Gb Cogent connection to CH2. Our other second switch was being used by the 100 Gb Crown Castle connection. There was a combination of programming changes and a cable change, in order to use that NY4 connection. This is not a normal scenario. We always have two connections available to us, and if one fails there is another one, with automatic failover to it. The issue relates, to this temporary transition to our new 100 Gb wavelength connection to CH2 and the fact that there was this firewall issue associated with it. The use of the new 100 Gb Cogent connection began the day before on June 10, 2025. Everything tested fine. Although we were unaware of the firewall issue. The plan was to decommission the Crown Castle connection and then use the NY4 connection as a backup. This had not yet occurred. Once there was a failure with the Crown Castle connection , the failover to the switch used by the Cogent connection could not connect to the NASDAQ TotalView server due to the firewall issue. One final note, our 10 Gb connection to NY4, will be upgraded to 100 Gb but this is four months away. It does take time to establish this amount of bandwidth between Michigan and Secaucus New Jersey over a dedicated wavelength. 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: 2025-06-13 01:57:16
|
| [2025-06-12 13:18:06] |
| Sierra_Chart Engineering - Posts: 19909 |
|
On the servers there is no missing NASDAQ TotalView historical data. If you are missing data in your -NQTV charts, and we would expect so, follow the instructions here: Historical Intraday Data (Missing Data / Download Errors / Viewing More Data): Retrying the Download When There is Data in the Chart 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: 2025-06-12 13:19:33
|
| [2025-06-12 22:13:46] |
| Sierra_Chart Engineering - Posts: 19909 |
|
This troublesome Crown Castle circuit is no longer being used by Sierra Chart. It has been permanently disconnected. And for the record, it went out approximately 12:30 PM Eastern time on June 11, 2025. It is still down to this moment. So we are at 30 hours. Apparently it did come up for a period of time like for an hour or so but there was some other fiber cut somewhere else. Also Crown Castle is selling off their fiber division to Zayo. 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: