Kinetick Connection disconnects today?

[number1]

I experienced several Kinetick connection losses today between 8:45AM - 9:00AM PST.

I am spending time going thru event logs to see if its my fault. Did anyone else experience drops (2 to be precise) today with their Kinetick NinjaTrader connections?

Thanks for any shared feedback. I have a support request already into Kinetick asking them the same. Just looking to save time diagnosing

Good luck out there.

Number1

[michrm]

I had a few days of disconnect from Kinetic at 11:45am and they keep saying it's my ISP. I checked with my ISP, everything is perfect. Very frustrating. have you resolved this? Would switching to CQG help?

[mschwager]

I had a few days of disconnect from Kinetic at 11:45am and they keep saying it's my ISP. I checked with my ISP, everything is perfect. Very frustrating. have you resolved this? Would switching to CQG help?

Hi, i also have sometimes (today, last week) disconnects at this time. Today it was at 11:05am. You too?

[NinjaTrader_Cameron]

Hello,

If you are receiving a disconnect from Kinetick I would suggest either opening a case with Kinetick or our NinjaTrader support staff so we can look into your situation further.

https://www.kinetick.com/support

Submit Request - http://www.ninjatrader.com/Support.php

[mschwager]

Hello,

If you are receiving a disconnect from Kinetick I would suggest either opening a case with Kinetick or our NinjaTrader support staff so we can look into your situation further.

https://www.kinetick.com/support

Submit Request - http://www.ninjatrader.com/Support.php

Yes Cameron, but the answer is always > CONTACT your ISP!

[mschwager]

I experienced several Kinetick connection losses today between 8:45AM - 9:00AM PST.

I am spending time going thru event logs to see if its my fault. Did anyone else experience drops (2 to be precise) today with their Kinetick NinjaTrader connections?

Thanks for any shared feedback. I have a support request already into Kinetick asking them the same. Just looking to save time diagnosing

Good luck out there.

Number1

Hello Number1,

i wanted to check in my log-files if i also had this disconnect on 17th april, but i have not the logfile from this date anymore. So please post any disconnects in this thread and i will reply shortly.

[mschwager]

Hi @all,

the support wanted a traceroute. So i sended them ...
---------------------------------------------------------------------------------
C:\>tracert interquote.com

Tracing route to interquote.com [69.41.208.42]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.99
2 9 ms 8 ms 10 ms bras2.ber.qsc.de [92.197.130.22]
3 8 ms 8 ms 8 ms core1.ber.qsc.de [87.234.13.141]
4 26 ms 25 ms 25 ms core1.fra.qsc.de [87.234.12.105]
5 23 ms 23 ms 23 ms l0.dblnir2-cr2.bbnplanet.net [195.16.160.5]
6 151 ms 150 ms 151 ms vlan70.csw2.Frankfurt1.Level3.net [4.69.154.126]
7 149 ms 149 ms 149 ms ae-71-71.ebr1.Frankfurt1.Level3.net [4.69.140.5]
8 149 ms 150 ms 149 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
9 150 ms 149 ms 150 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.50]
10 151 ms 151 ms 151 ms ae-47-47.ebr2.Washington12.Level3.net [4.69.202.58]
11 158 ms 152 ms 151 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
12 149 ms 149 ms 149 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
13 150 ms 150 ms 150 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
14 149 ms 151 ms 150 ms ae-22-52.car2.Denver1.Level3.net [4.69.147.100]
15 159 ms 158 ms 158 ms DTN.car2.Denver1.Level3.net [4.53.2.94]
16 161 ms 160 ms 161 ms 66.112.152.58
17 161 ms 160 ms 160 ms 69.41.208.42

Trace complete.
---------------------------------------------------------------------------------

The answer was a bit funny.
>>>> "... You can see the time it takes for each of the servers listed in the trace route to respond. Starting at the 6th listing, the delays increase by a large amount. These delays can cause the time out message you have received. ..."

This must be a joke!

On CQG/Continuum i have sometimes up to 300ms and i dont have any disconnects here. Perhabs Kinetick must configure the (waiting-)response-time on his servers, when it really is the problem. I think not. The problem is somewhere else in this infrastructure. When 160ms is the problem, why it is not every day? Why just sometimes? 160ms is def not the problem. I would say 160ms is good and i think there are traders in the US which have more than 160ms.

[NinjaTrader_Cameron]

Hello,

Different APIs have different sensitivities to latency.

Please continue working directly with Kinetick on this issue via direct email.