66.109.7.162 (TWC owned node malfunction) - Time Warner Internet

#1
This question is about "66.109.7.162 (TWC owned node malfunction)", with Time Warner Cable internet and apps. Server is slow when it works, it is often offline completly.

It doesn't show in all sites. It shows in 99%. In fact the only site I found that it doesn't show is google.com.
Here is the trace to google.
Tracing route to www.google.com [172.217.4.228]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.0.2.1
2 9 ms 2 ms 2 ms 192.168.0.1
3 20 ms 11 ms 9 ms 142.254.154.117
4 26 ms 22 ms 30 ms ae63.hdbgky0401h.midwest.rr.com [74.128.5.25]
5 13 ms 11 ms 13 ms be30.rcmdkyat01r.midwest.rr.com [65.29.28.110]
6 31 ms 27 ms 28 ms be26.clevohek01r.midwest.rr.com [65.189.140.170]
7 35 ms 36 ms 36 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 34 ms 34 ms 34 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
9 47 ms 34 ms 35 ms 216.50.76.41
10 35 ms 33 ms 34 ms 207.88.14.190.ptr.us.xo.net [207.88.14.190]
11 36 ms 34 ms 35 ms 207.88.14.165.ptr.us.xo.net [207.88.14.165]
12 42 ms 46 ms 51 ms 216.50.79.62
13 58 ms 53 ms 58 ms 216.239.62.143
14 36 ms 35 ms 83 ms 72.14.236.148
15 43 ms 40 ms 40 ms 108.170.237.42
16 58 ms 65 ms 62 ms 108.170.232.166
17 40 ms 40 ms 40 ms 108.170.243.161
18 45 ms 41 ms 40 ms 108.170.233.85
19 39 ms 40 ms 41 ms ord30s31-in-f4.1e100.net [172.217.4.228]
Trace complete.

Here is a trace to pinggoat.com

Tracing route to www.pinggoat.com [167.114.156.214]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.0.2.1
2 2 ms 4 ms 2 ms 192.168.0.1
3 12 ms 14 ms 9 ms 142.254.154.117
4 24 ms 28 ms 30 ms ae63.hdbgky0401h.midwest.rr.com [74.128.5.25]
5 16 ms 13 ms 11 ms be30.rcmdkyat01r.midwest.rr.com [65.29.28.110]
6 29 ms 31 ms 30 ms be26.clevohek01r.midwest.rr.com [65.189.140.170]
7 41 ms 36 ms 36 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 35 ms 35 ms 34 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
9 * 2242 ms * 66.109.7.162
10 * * * Request timed out.
11 40 ms 61 ms 40 ms be100-104.nwk-1-a9.nj.us [192.99.146.253]
12 51 ms 48 ms 49 ms be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
13 48 ms 48 ms 50 ms vl20.bhs-g1-a75.qc.ca [198.27.73.229]
14 50 ms 48 ms 49 ms be50-5.bhs-3b-a9.qc.ca [198.27.73.96]
15 49 ms 47 ms 48 ms dmpro-ca-01.fooservers.com [167.114.156.214]
Trace complete.

Here is a trace to www.qperfectdesign.com

Tracing route to qperfectdesign.com [23.254.201.204]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.0.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 12 ms 10 ms 10 ms 142.254.154.117
4 30 ms 29 ms 29 ms ae63.hdbgky0401h.midwest.rr.com [74.128.5.25]
5 14 ms 11 ms 13 ms be30.rcmdkyat01r.midwest.rr.com [65.29.28.110]
6 33 ms 28 ms 43 ms be26.clevohek01r.midwest.rr.com [65.189.140.170]
7 37 ms 36 ms 36 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 32 ms 36 ms 57 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
9 1679 ms 2219 ms * ge-7-1-6.pr0.chi10.tbone.rr.com [66.109.9.74]
10 * * * Request timed out.
11 * * * Request timed out.
12 63 ms 63 ms 64 ms client-23-238-104-129.hostwindsdns.com [23.238.104.129]
13 60 ms 62 ms 70 ms 192.119.77.7
14 62 ms 64 ms 63 ms client-23-254-201-204.hostwindsdns.com [23.254.201.204]
Trace complete.

We have had multiple techs out multiple times and we are told there is no issue. I showed the results to the techs and I was told there was nothing that could be done it was just something I would have to live with. It causes a lot of issues and is unacceptable.


This topic covered 66.109.7.162 (TWC owned node malfunction), and TWC cable internet service.
 
Top