Kinetick Data Drop

[molecool]

I'm seeing this intermittently in my new server hosted in a data center in Philadelphia near 7signal. Just dropped the signal and the traceroute was executed immediately:

Tracing route to 7signal.com [66.39.116.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  104.193.10.1
  2    <1 ms    <1 ms    <1 ms  199.19.111.65
  3    <1 ms    <1 ms    <1 ms  162.213.24.25
  4     9 ms     9 ms    10 ms  78.152.57.82
  5     9 ms     9 ms     9 ms  eth5-4.core1.nyc1.us.as5580.net [78.152.35.239]
  6    14 ms    16 ms    14 ms  eth3-1.core1.ash2.us.as5580.net [78.152.45.193]
  7    14 ms    21 ms    14 ms  ae0-0.edge1.ash2.us.as5580.net [78.152.34.61]
  8    18 ms    33 ms    42 ms  78.152.46.130
  9    20 ms    20 ms    20 ms  pit-edge-01.inet.qwest.net [67.14.56.26]
 10    22 ms    22 ms    22 ms  63-235-56-154.dia.static.qwest.net [63.235.56.154]
 11     *        *        *     Request timed out.
 12    20 ms    20 ms    20 ms  7signal.com [66.39.116.39]

Trace complete.


$ 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  104.193.10.1
  2    <1 ms    <1 ms    <1 ms  199.19.111.65
  3    <1 ms    <1 ms    <1 ms  162.213.24.250
  4     *        *        *     Request timed out.
  5     9 ms     9 ms     9 ms  eth5-4.core1.nyc1.us.as5580.net [78.152.35.239]
  6    14 ms    14 ms    14 ms  eth3-1.core1.ash2.us.as5580.net [78.152.45.193]
  7    14 ms    14 ms    15 ms  ae0-0.edge1.ash2.us.as5580.net [78.152.34.61]
  8    17 ms    19 ms    19 ms  78.152.46.130
  9    58 ms    58 ms    58 ms  kcm-edge-18.inet.qwest.net [67.14.11.210]
 10    66 ms    65 ms    66 ms  65.116.176.82
 11    60 ms    60 ms    60 ms  66.112.152.50
 12    60 ms    60 ms    60 ms  69.41.208.42

Trace complete.

Seems like the problem is partially on your end as it timed out on the second to last hop. On Interquote (Nebraska) there is a timeout outside your domain it seems.

[NinjaTrader_Brandon]

Hello molecool,

Thanks for your post.

The Kinetick servers are working without issue at this time.
These results you provided seems to match the results you sent in to platform support 3 days ago.
Note that time outs can be expected as not all servers allow a tracert to them.
When you see these same results when the connection works/over various periods of time this would indicate that the specific server does not allow the tracert.
There have been no issues with the Kinetick server recently and these tracert results do not seem to capture the connection issue for your ISP to look into.

[molecool]

I think you're right - I just performed the same traceroute from home and the second to last hop timed out again. So it's possible whatever that is - it's refusing the traceroute. Which of course doesn't help if one attempts to figure out where problems occur.