Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I have a regular problem with downloading replay data (not exchange data).
I have also made a few trace route tests with ping plotter.
Deutsche Telekom sometimes routes via the server 80.157.128.230 and sometimes routes via 80.156.161.46. In both cases there are similar problems. I would therefore exclude that one of these routing servers is responsible for the packet loss.
The problem is generated by the US servers, and the Telekom servers seem to no longer support the connection once the US servers have already lost the connection.
Again this is the behaviour with the server for replay data. The problem server is a 7ticks.com server with the IP address 64.202.118.181 , which is located in Chicago.
Is anybody capable of downloading replay data right now?
@Daytrader999: Could not download any data from the replay server today. I am in touch with Deutsche Telekom, they will call me back during the next days.
But I have no clue, whether this is a Deutsche Telekom problem or not.
I was able to download market data replay today, from France and from New-Jersey.
According to your screenshots, the problem is on the European side of the Atlantic.
I'm not sure, but the download seems longer than usual, more than 4 minutes for ES 03-13, Jan 14th, level 1 and 2,
I currently use a O2 mobile internet connection. O2 is a subsidiary of Telefonica, and as far as I know they do not use servers from Deutsche Telekom. The latency is about 100 ms worse than the fixed line, so I am approx. 30 ms away from Chicago, where the data server is located.
Replay data is downloaded at an average speed of about 36.000 B/s. The download of the ES level 1 and 2 data files took 8 minutes (5, 599 kByte and 11,856 kByte) files.
Testing data download with Deutsche Telekom
I have now switched back to my main Internet connection, which relies on Deutsche Telekom. I am now downloading exactly the same data files from the 7ticks server as before. First thing that is striking is that the resource center of the task manager shows lower speeds - around 3.000 B/s compared to the =O2 connection.
I have now waited for 15 minutes. NinjaTrader frooze while trying to download data and I have to remove it with the task manager. The problem seems to be aggravated by a NinjaTrader bug.
Conclusion
Deutsche Telekom does have a routing problem somewhere, as is shown. The likely cause is the router with the IP address 80.157.128.230, which may have capacity problems or maybe damaged. I will call them again on Monday.
NinjaTrader freezes, if the data connection is unstable and cannot be used any more.
Do you get the same latency and other issues if you do a Speedtest on a server in Chicago. What happens if you just try to load a URL of a web site based on a Chicago server (eg may be a Chicago tourism site where you could assume their server would be in Chicago).
The fact that you can down load off your mobile (I assume 3G) connection, but not your landline ADSL connection has all the hallmarks of data shaping/profiling/throttling that I experienced in NZ at one time and wrote in detail about the other day in the other thread.
When I had my issues I could maintain an absolutely perfect connection (although with higher latency) to ZF over a mobile 3 G broadband connection with the SAME provider who was supplying me with my landline ADSL broadband connection.
This was one of the ways I isolated my problem to something the ISP was doing (ie Telecom NZ were supplying my landline, ADSL broadband, mobile 3G broadband and were my ISP) so the fact that the ADSL had frequent disconnections yet the 3G didn't meant it was the ISP.
As I wrote in the other post that were shaping the data on the ADSL to give everyone a fair share of capacity at peak times and they were doing this by trying to restrict users downloading files and streaming and they can do this without affecting those just surfing a URL. Unfortunately futures trading data gets transmitted to us in a format that is the same type of data that the ISP's are trying to restrict ie they see it as file downloading or streaming data.
I would be really pushing that German ISP to open up and discuss their data shaping policy, or at least get them to confirm in writing they don't do this at which point you have isolated that as not being the issue.
Another test I did that I forgot to write about in the other post is that when I had my issues I started blaming NT and ZF (as we all do). ZF were convinced the issue was not at their end (and they ended up being correct). In order to help prove this they gave me access to ZF beta Web Trader platform and I was able to have my live account connected to ZF via NT and the ZF Web Trader platform at the SAME time.
The result: while I was getting frequent data drops on the NT related ZF connection I was having NO drops or freezing or delays on the ZF Web Trader platform.
The reason: data shaping by my ISP. The connection via NT is treated as bad data by the ISP for data shaping ie it is seen as file/torrent downloading or streaming whereas the connection via ZF Web Trader platform is seen as normal URL surfing by the ISP and is not shaped/throttled/profiled.
