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 ran this discussion past our engineeers and was informed that dynamic IP addresses will not cause disconnections to IQFeed/Kinetick servers. The vast majority of internet users throughout the world have a dynamic IP address although most broadband connections change pretty rarely since they are always on by design.
Engineers say this is not correct and actually the converse is true. If the customer has an IP address that has changed, it means he has gotten disconnected and has reconnected.
In the end, it is actually the disconnection/reconnection process (not the IP Dynamic address) that is the issue.
Thanks for clarification Robert. My broadband connection is always on whilst trading so should not see IP change change as you say. So data issue not the result of such dynamic IPs.
I had a NinjaTrader/Kinetick disconnection yesterday, but my IP address did NOT change. Hence, my broadband connection remained ON - but Ninja/Kinetick data connection was still lost briefly.
My intention of following IP change is to test if my broadband is momentarily disconnecting causing the knock-on effect of Ninja reporting same. For this first test case, broadband stayed on, but data connection was lost - so problem this time lies somewhere beyond my PC along the path to the Ninja or Kinetick/IQFeed servers. Will continue to monitor.
One question: Do your engineers support advice that using the direct IQFeed client to access data is more reliable than a straight Kinetick connection? This advice has been given out to others. Is it true or just a myth?
My personal advice on this is exactly the opposite if that data is used in NT7; especially if you are using IQFeed Client newer versions.
My disconnection problems with NT7 were all due to local software conflicting together (i.e. NT7 and IQFeed Client), and none related to dynamic IPs, servers, internet routes, ISPs, VPNs, etc...
I've found that by eliminating that piece of software in the middle, and connecting directly to Kinetick from within NT7 was the most stable option for me.
On a side note though, if you want to access the real-time data feed servers and transmit these data to external software like matlab, excel, or other platforms, sierrachart and the like... Then yes, using IQFeed Client is the most stable, and highly recommended.
I believe, the engineers should work with NinjaTrader to make their interfaces reciprocally compatible with the latest version release of either software.
Successful people will do what unsuccessful people won't or can't do!
IQFeed and Kinetick streaming tick data are identical in terms of reliability and accuracy. IQFeed historical data is from our historical servers (and matches tick exactly), and NT historical is from its own servers.
We have over 1000 developers currently writing to IQFeed, including NT and 70 other top software partners. Because we are always working on improving IQFeed, we are very proactive in providing all developers a beta of the next version well in advance of release to ensure compatibility and to resolve potential issues.
I'm a noob trader, but a bit of an IT geek- so i can finally contribute a little something. Yay! I've worked in IT since 1999, and my last job was at Dell as a senior sales rep for anything related to a datacenter.
As such, i was reading page 1 and quite honestly getting a bit annoyed when i saw comments about Dynamic IP being blamed. Luckily IQFeed corrected that statement- because as pointed out, the vast majority of the world runs on dynamic IP's.
The command to find your IP in a dos command prompt is "ipconfig" or "ipconfig /all" which will give more stats. However this will list your internal IP(likely something like 192.168.*.*), which tbh is irrelevant. Your external IP usually sits in your router which is connected to your ISP.
Tons of sites will list your external IP, google "whats my ip". Or just use speedtest.net or even pingtest.net to find your IP and also do a decent connection test. Remember to choose a test-server physically located as close as possible to the servers you're trying to reach (in this case, IQfeeds). This will however only give you a _then and there_ picture of your connection to something "close" to your target. Not very accurate, at all.
The ideal test is using something like pingplotter (a great tool, get the free version) to systematically ping a server at certain intervals. If you can find the IP to IQFeeds servers, like Bob seems to have done, then this is the most precise way to test actual health of your connection to IQfeeds servers because connections can exhibit erratic behaviour (ie fine 95% of the time then spiking for some reason). Keep in mind tho that datacenters usually mask or disallow pings to avoid stuff like ddos attacks.
Anywho.. what troubles me in all honesty, from an IT guy's perspective, is the insinuation that they are running their services from their own datacenter/building. At least in Europe/Scandinavia this is a sub par choice. You would want your mission critical servers hosted in a "real" datacenter cluster, run by Verizon, AT&T, or the likes. Something that guarantees available compute power, bandwidth, latency, uptime, and has multiple backup solutions (power, internet connections etc) for any possible disaster situation. These datacenters will take data routing very seriously, and reroute/load balance nodes that appear overloaded on their backbones and also contact other major providers to tweak theirs if they find errors (this actually already happens automatically to a certain degree).
Unless you are Google or Facebook, having live feedservers in the office building, on a connection which is shared with other companies of that building, is a frightening thought. I certainly hope this is not the case for any data provider. There are severe limitations to how much safety you can get out of your in house datacenter, unless you are spending extraordinary amounts of $$$ on it.