DTN IQFeed, DTN.IQ, DTN ProphetX Support Forums

Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)

"Awesome response, as usual. It is a sincere and refreshing pleasure to do business with DTN, compared to your competition." - Comment from Ryan

"I used to have *******, but they are way more money for the same thing. I have had no probs with data from DTN since switching over." - Comment from Public Forum Post

"As a past ******* customer(and not a happy one), IQ Feed by DTN is a much better and cheaper product with great customer support. I have had no problems at all since switching over." - Comment from Public Forum

"I just wanted to say how happy I am with your service. I was able to download the API docs last week and I was able to replicate Interactive Brokers historical bar queries and realtime bar queries over the weekend. That was about one of the fastest integrations that I've ever done and it works perfectly!!!!" - Comment from Jason via Email

"The service is great, I see a noticeable improvement in my volume profiles over [broker]'s data feed" - Comment from Larry

"Thanks for following up with me. You guys do a great job in tech support." - Comment from Phelps

"I started a trial a few weeks back before the market went wild. DTN.IQ didn’t miss anything and beat my other provider. I decided to stay with you because of the great service through all the volatility." - Comment from Mike

"You are either overstaffed or people just don't have problems with your feed because customer support always answers the phone quickly." - Comment from Jay via Email

"Excellent datafeed !!!" - Comment from Arely

"You are much better than lawyers or the phone company because you answer the phone when I call! I just love your customer service." - Comment from Isreal

Home

Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather

DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter

»Forums Index »Archive (2017 and earlier) »IQFeed Developer Support »Repeated disconnections on May 9

Author	Topic: Repeated disconnections on May 9 (3 messages, Page 1 of 1)
dk_brad -Interested User- Posts: 12 Joined: May 11, 2014	Posted: May 12, 2014 12:13 AM Msg. 1 of 3 Per the subject, I experienced repeated disconnections last Friday. IQConnect started and logged in at ~09:53:38Z (UTC). Over the next few seconds, the following local connections were established: 11 connections to port 9100 (lookup) 2 connections to port 5009 (L1) The L1 connections both reported the remote IP as 66.112.156.223/60002. At approximately 14:18Z, the following sequence of disconnection/reconnection occurred. C1/C2 refers to the two L1 port connections. 14:18:49.933Z: C1 [SERVER DISCONNECTED] 14:18:49.933Z: C2 [SERVER DISCONNECTED] 14:18:50.164Z: C1 [SERVER DISCONNECTED] 14:18:50.164Z: C2 [SERVER DISCONNECTED] 14:21:18.834Z: C1 [SERVER DISCONNECTED] 14:21:18.834Z: C2 [SERVER DISCONNECTED] 14:22:22.886Z: C1 [KEY] 14:22:22.886Z: C1 [SERVER CONNECTED] 14:22:22.886Z: C2 [KEY] 14:22:22.886Z: C2 [SERVER CONNECTED] 14:22:22.886Z: C2 [IP] 14:22:22.886Z: C1 [IP] 14:22:22.886Z: C2 [CUST (ip/port=66.112.156.222/60003)] 14:22:22.886Z: C1 [CUST (ip/port=66.112.156.222/60003)] 14:23:28.933Z: C1 [SERVER DISCONNECTED] 14:23:28.933Z: C2 [SERVER DISCONNECTED] 14:23:54.840Z: C1 [SERVER DISCONNECTED] 14:23:54.840Z: C2 [SERVER DISCONNECTED] 14:24:07.016Z: C1 [SERVER DISCONNECTED] 14:24:07.016Z: C2 [SERVER DISCONNECTED] 14:24:57.669Z: C1 [SERVER DISCONNECTED] 14:24:57.669Z: C2 [SERVER DISCONNECTED] 14:26:10.663Z: C1 [KEY] 14:26:10.663Z: C1 [SERVER CONNECTED] 14:26:10.663Z: C2 [KEY] 14:26:10.663Z: C1 [IP] 14:26:10.663Z: C2 [SERVER CONNECTED] 14:26:10.663Z: C1 [CUST (ip/port=66.112.156.223/60002)] 14:26:10.663Z: C2 [IP] 14:26:10.663Z: C2 [CUST (ip/port=66.112.156.223/60002)] 14:26:33.933Z: C1 [SERVER DISCONNECTED] 14:26:33.933Z: C2 [SERVER DISCONNECTED] 14:26:45.778Z: C1 [SERVER DISCONNECTED] 14:26:45.778Z: C2 [SERVER DISCONNECTED] 14:26:45.986Z: C1 [KEY] 14:26:45.986Z: C1 [SERVER CONNECTED] 14:26:45.986Z: C2 [KEY] 14:26:45.986Z: C2 [SERVER CONNECTED] 14:26:45.986Z: C1 [IP] 14:26:45.986Z: C2 [IP] 14:26:45.986Z: C1 [CUST (ip/port=66.112.156.229/60003)] 14:26:45.986Z: C2 [CUST (ip/port=66.112.156.229/60003)] 14:28:37.934Z: C1 [SERVER DISCONNECTED] 14:28:37.934Z: C2 [SERVER DISCONNECTED] 14:28:49.937Z: C1 [SERVER DISCONNECTED] 14:28:49.937Z: C2 [SERVER DISCONNECTED] 14:29:06.235Z: C1 [SERVER DISCONNECTED] 14:29:06.235Z: C2 [SERVER DISCONNECTED] 14:29:27.410Z: C1 [KEY] 14:29:27.410Z: C1 [SERVER CONNECTED] 14:29:27.410Z: C2 [KEY] 14:29:27.410Z: C2 [SERVER CONNECTED] 14:29:27.410Z: C1 [IP] 14:29:27.410Z: C1 [CUST (ip/port=66.112.148.114/60002)] 14:29:27.410Z: C2 [IP] 14:29:27.410Z: C2 [CUST (ip/port=66.112.148.114/60002)] 14:30:19.933Z: C1 [SERVER DISCONNECTED] 14:30:19.933Z: C2 [SERVER DISCONNECTED] 14:30:31.531Z: C1 [SERVER DISCONNECTED] 14:30:31.531Z: C2 [SERVER DISCONNECTED] 14:30:44.175Z: C1 [KEY] 14:30:44.175Z: C1 [SERVER CONNECTED] 14:30:44.175Z: C1 [IP] 14:30:44.175Z: C2 [KEY] 14:30:44.175Z: C2 [SERVER CONNECTED] 14:30:44.175Z: C1 [CUST (ip/port=66.112.156.115/60003)] 14:30:44.175Z: C2 [IP] 14:30:44.175Z: C2 [CUST (ip/port=66.112.156.115/60003)] 14:30:53.935Z: C1 [SERVER DISCONNECTED] 14:30:53.935Z: C2 [SERVER DISCONNECTED] 14:31:08.784Z: C1 [SERVER DISCONNECTED] 14:31:08.784Z: C2 [SERVER DISCONNECTED] 14:31:14.947Z: C1 [SERVER DISCONNECTED] 14:31:14.949Z: C2 [SERVER DISCONNECTED] 14:31:25.383Z: C1 [KEY] 14:31:25.383Z: C1 [SERVER CONNECTED] 14:31:25.383Z: C2 [KEY] 14:31:25.383Z: C2 [SERVER CONNECTED] 14:31:25.384Z: C1 [IP] 14:31:25.384Z: C1 [CUST (ip/port=66.112.156.224/60003)] 14:31:25.384Z: C2 [IP] 14:31:25.384Z: C2 [CUST (ip/port=66.112.156.224/60003)] This continued for some time. Was there an issue with your service during this time? If not, are you aware of what may cause this? (FYI, Level3 is the only network between my host and your servers). I have confirmed with my hosting provider that they had no connectivity issues at that time.
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: May 12, 2014 02:56 PM Msg. 2 of 3 There weren't any known issues with our servers at that time. I also checked through the login logs (where I was able to verify the information in your post) but there wasn't anything there to indicate there was any significant (or even insignificant) event at that time. Assuming you are correct that Level 3 handles everything between your provider and us, we can only assume this was an unreported localized issue with Level 3.
dk_brad -Interested User- Posts: 12 Joined: May 11, 2014	Posted: May 13, 2014 01:00 AM Msg. 3 of 3 Thanks for the quick response. I agree that without additional data, there's little else to conclude. I've put in place monitoring and logging of the route, so if the issue occurs again, we shall have more information to assess the likely cause. My server is located in a NJ data center and is only a few ms and hops to the NY based exchanges and my broker. I have never had a network issue (> 1 year), but my previous data provider was also NY based. I've only been running IqFeed as a live data source for four days. For reference, this is the route to your solar2 server: 1 x.x.x.x (x.x.x.x) 0.586 ms 0.645 ms 0.771 ms 2 207.99.53.41 (207.99.53.41) 0.408 ms 0.423 ms 0.421 ms 3 0.e1-1.tbr1.tl9.nac.net (209.123.10.102) 1.411 ms 1.405 ms 0.e1-3.tbr2.mmu.nac.net (209.123.10.26) 0.476 ms 4 0.e1-1.tbr2.tl9.nac.net (209.123.10.78) 1.367 ms 1.459 ms 1.439 ms 5 xe-11-1-3.edge8.NewYork1.Level3.net (4.31.30.37) 1.632 ms 1.626 ms 1.597 ms 6 vlan70.csw2.NewYork1.Level3.net (4.69.155.126) 47.160 ms 47.200 ms vlan60.csw1.NewYork1.Level3.net (4.69.155.62) 47.182 ms 7 ae-92-92.ebr2.NewYork1.Level3.net (4.69.148.45) 46.057 ms ae-72-72.ebr2.NewYork1.Level3.net (4.69.148.37) 45.837 ms ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41) 45.967 ms 8 ae-48-48.ebr2.NewYork2.Level3.net (4.69.201.38) 46.794 ms 46.769 ms ae-45-45.ebr2.NewYork2.Level3.net (4.69.141.22) 46.835 ms 9 ae-2-2.ebr1.Chicago1.Level3.net (4.69.132.65) 47.130 ms 46.793 ms 48.258 ms 10 ae-6-6.ebr1.Chicago2.Level3.net (4.69.140.190) 46.733 ms 47.003 ms 46.965 ms 11 ae-3-3.ebr2.Denver1.Level3.net (4.69.132.61) 47.258 ms 46.994 ms 46.978 ms 12 ae-22-52.car2.Denver1.Level3.net (4.69.147.100) 222.894 ms 222.742 ms 222.645 ms 13 DTN.car2.Denver1.Level3.net (4.53.2.94) 56.465 ms 57.481 ms 57.469 ms 14 66.112.152.58 (66.112.152.58) 59.367 ms 59.374 ms 59.263 ms 15 solar2.interquote.com (66.112.156.222) 56.198 ms !X 56.680 ms !X 56.858 ms !X I just ran a 5 minute test on this route with the following results: Host Loss% Snt Last Avg Best Wrst StDev 1. x.x.x.x 0.0% 377 1.0 0.9 0.5 17.8 0.9 2. 207.99.53.41 0.0% 377 0.6 1.6 0.4 33.7 2.9 3. 0.e1-3.tbr2.mmu.nac.net 0.0% 377 0.7 2.6 0.5 28.8 3.4 4. 0.e1-1.tbr2.tl9.nac.net 0.0% 377 1.5 2.1 1.4 24.5 1.9 5. xe-11-1-3.edge8.NewYork1.Level3.net 0.0% 376 1.8 2.9 1.6 59.4 5.8 6. vlan70.csw2.NewYork1.Level3.net 0.0% 376 47.4 47.6 46.9 61.1 1.8 7. ae-72-72.ebr2.NewYork1.Level3.net 0.0% 376 46.4 46.6 46.0 60.5 1.5 8. ae-47-47.ebr2.NewYork2.Level3.net 0.0% 376 46.9 47.4 46.9 59.2 1.3 ae-48-48.ebr2.NewYork2.Level3.net ae-46-46.ebr2.NewYork2.Level3.net ae-45-45.ebr2.NewYork2.Level3.net 9. ae-2-2.ebr1.Chicago1.Level3.net 0.0% 376 47.0 47.3 46.6 58.7 1.6 10. ae-6-6.ebr1.Chicago2.Level3.net 0.0% 376 48.3 47.4 46.6 72.6 2.3 11. ae-3-3.ebr2.Denver1.Level3.net 0.0% 376 48.4 47.4 46.6 71.0 1.8 12. ae-22-52.car2.Denver1.Level3.net 0.0% 376 165.6 68.9 46.6 278.2 47.0 13. DTN.car2.Denver1.Level3.net 0.0% 376 58.2 67.5 57.2 899.8 56.1 14. 66.112.152.58 0.0% 376 58.0 58.3 57.2 200.8 7.4 15. solar2.interquote.com 0.0% 376 57.0 57.2 56.8 69.0 0.8 Even at this time (1:30AM EST), although all packets are getting through, there seem to be some issues around the node DTN.car2.Denver1.Level3.net, with latency of up to 900ms and significant jitter. I presume this is where your data center connects with Level3. This may just be ICMP rate limiting though, since the final node shows no such jitter. Edited by dk_brad on May 13, 2014 at 01:13 AM