- May 22, 2011
- 21
- 0
- 0
So I've recently moved and got on to Time Warner Cable which I suspect is my problem.
I have an Asus AC88U Router, with an Archer T8E AC PCIE chip in my PC.
PC is windows 10 x64.
If I run ping -t it ends up looking something like this:
Reply from 216.58.219.206: bytes=32 time=85ms TTL=50
Reply from 216.58.219.206: bytes=32 time=26ms TTL=50
Reply from 216.58.219.206: bytes=32 time=68ms TTL=50
Reply from 216.58.219.206: bytes=32 time=60ms TTL=50
Reply from 216.58.219.206: bytes=32 time=23ms TTL=50
Reply from 216.58.219.206: bytes=32 time=46ms TTL=50
Reply from 216.58.219.206: bytes=32 time=58ms TTL=50
Reply from 216.58.219.206: bytes=32 time=37ms TTL=50
Reply from 216.58.219.206: bytes=32 time=35ms TTL=50
Reply from 216.58.219.206: bytes=32 time=1041ms TTL=50
Reply from 216.58.219.206: bytes=32 time=228ms TTL=50
Reply from 216.58.219.206: bytes=32 time=28ms TTL=50
Reply from 216.58.219.206: bytes=32 time=509ms TTL=50
Reply from 216.58.219.206: bytes=32 time=733ms TTL=50
Reply from 216.58.219.206: bytes=32 time=959ms TTL=50
Reply from 216.58.219.206: bytes=32 time=305ms TTL=50
Reply from 216.58.219.206: bytes=32 time=308ms TTL=50
Reply from 216.58.219.206: bytes=32 time=315ms TTL=50
Reply from 216.58.219.206: bytes=32 time=932ms TTL=50
Reply from 216.58.219.206: bytes=32 time=931ms TTL=50
Reply from 216.58.219.206: bytes=32 time=52ms TTL=50
Reply from 216.58.219.206: bytes=32 time=128ms TTL=50
Reply from 216.58.219.206: bytes=32 time=552ms TTL=50
On a mac with the ping -t the spikes come far less frequently, but they still come.
Tracert looks like this:
Tracing route to google.com [173.194.123.40]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 27 ms 34 ms 18 ms cpe-107-15-32-1.nc.res.rr.com [107.15.32.1]
3 203 ms 32 ms 198 ms cpe-174-111-124-125.triad.res.rr.com [174.111.124.125]
4 36 ms 330 ms 34 ms cpe-024-025-063-078.ec.res.rr.com [24.25.63.78]
5 39 ms 431 ms 13 ms 24.93.67.200
6 505 ms 21 ms 399 ms bu-ether45.asbnva1611w-bcr00.tbone.rr.com [107.14.19.44]
7 201 ms 148 ms 20 ms 0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
8 335 ms 170 ms 27 ms 209.48.38.225
9 34 ms 502 ms 44 ms 209.48.42.54
10 580 ms 30 ms 73 ms 216.239.46.248
11 35 ms 23 ms 368 ms 72.14.236.98
12 259 ms 646 ms 30 ms 216.239.40.165
13 32 ms 25 ms 390 ms 209.85.246.5
14 53 ms 30 ms 273 ms 209.85.240.113
15 111 ms 46 ms 74 ms lga15s47-in-f8.1e100.net [173.194.123.40]
Trace complete.
Tracing route to google.com [74.125.226.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 37 ms 160 ms 196 ms cpe-107-15-32-1.nc.res.rr.com [107.15.32.1]
3 213 ms 24 ms 775 ms cpe-174-111-124-101.triad.res.rr.com [174.111.124.101]
4 692 ms 238 ms 16 ms cpe-024-025-063-078.ec.res.rr.com [24.25.63.78]
5 541 ms 82 ms 78 ms be31.drhmncev01r.southeast.rr.com [24.93.64.184]
6 89 ms 254 ms 26 ms bu-ether45.asbnva1611w-bcr00.tbone.rr.com [107.14.19.44]
7 565 ms 24 ms 141 ms 0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
8 70 ms 63 ms 270 ms 209.48.38.225
9 237 ms 171 ms 144 ms 209.48.42.54
10 587 ms 333 ms 45 ms 216.239.46.248
11 59 ms 110 ms 27 ms 72.14.236.98
12 222 ms 25 ms 43 ms 216.239.40.165
13 170 ms 24 ms 92 ms 209.85.252.243
14 29 ms 408 ms 39 ms 209.85.245.177
15 126 ms 329 ms 46 ms lga15s42-in-f8.1e100.net [74.125.226.8]
Trace complete.
The tracert makes me think that the problem is on Time Warner's end because the route up until the cable modem is always low. Thoughts? Suggestions?
I'm having a twc tech come out later today.
I have an Asus AC88U Router, with an Archer T8E AC PCIE chip in my PC.
PC is windows 10 x64.
If I run ping -t it ends up looking something like this:
Reply from 216.58.219.206: bytes=32 time=85ms TTL=50
Reply from 216.58.219.206: bytes=32 time=26ms TTL=50
Reply from 216.58.219.206: bytes=32 time=68ms TTL=50
Reply from 216.58.219.206: bytes=32 time=60ms TTL=50
Reply from 216.58.219.206: bytes=32 time=23ms TTL=50
Reply from 216.58.219.206: bytes=32 time=46ms TTL=50
Reply from 216.58.219.206: bytes=32 time=58ms TTL=50
Reply from 216.58.219.206: bytes=32 time=37ms TTL=50
Reply from 216.58.219.206: bytes=32 time=35ms TTL=50
Reply from 216.58.219.206: bytes=32 time=1041ms TTL=50
Reply from 216.58.219.206: bytes=32 time=228ms TTL=50
Reply from 216.58.219.206: bytes=32 time=28ms TTL=50
Reply from 216.58.219.206: bytes=32 time=509ms TTL=50
Reply from 216.58.219.206: bytes=32 time=733ms TTL=50
Reply from 216.58.219.206: bytes=32 time=959ms TTL=50
Reply from 216.58.219.206: bytes=32 time=305ms TTL=50
Reply from 216.58.219.206: bytes=32 time=308ms TTL=50
Reply from 216.58.219.206: bytes=32 time=315ms TTL=50
Reply from 216.58.219.206: bytes=32 time=932ms TTL=50
Reply from 216.58.219.206: bytes=32 time=931ms TTL=50
Reply from 216.58.219.206: bytes=32 time=52ms TTL=50
Reply from 216.58.219.206: bytes=32 time=128ms TTL=50
Reply from 216.58.219.206: bytes=32 time=552ms TTL=50
On a mac with the ping -t the spikes come far less frequently, but they still come.
Tracert looks like this:
Tracing route to google.com [173.194.123.40]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 27 ms 34 ms 18 ms cpe-107-15-32-1.nc.res.rr.com [107.15.32.1]
3 203 ms 32 ms 198 ms cpe-174-111-124-125.triad.res.rr.com [174.111.124.125]
4 36 ms 330 ms 34 ms cpe-024-025-063-078.ec.res.rr.com [24.25.63.78]
5 39 ms 431 ms 13 ms 24.93.67.200
6 505 ms 21 ms 399 ms bu-ether45.asbnva1611w-bcr00.tbone.rr.com [107.14.19.44]
7 201 ms 148 ms 20 ms 0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
8 335 ms 170 ms 27 ms 209.48.38.225
9 34 ms 502 ms 44 ms 209.48.42.54
10 580 ms 30 ms 73 ms 216.239.46.248
11 35 ms 23 ms 368 ms 72.14.236.98
12 259 ms 646 ms 30 ms 216.239.40.165
13 32 ms 25 ms 390 ms 209.85.246.5
14 53 ms 30 ms 273 ms 209.85.240.113
15 111 ms 46 ms 74 ms lga15s47-in-f8.1e100.net [173.194.123.40]
Trace complete.
Tracing route to google.com [74.125.226.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 37 ms 160 ms 196 ms cpe-107-15-32-1.nc.res.rr.com [107.15.32.1]
3 213 ms 24 ms 775 ms cpe-174-111-124-101.triad.res.rr.com [174.111.124.101]
4 692 ms 238 ms 16 ms cpe-024-025-063-078.ec.res.rr.com [24.25.63.78]
5 541 ms 82 ms 78 ms be31.drhmncev01r.southeast.rr.com [24.93.64.184]
6 89 ms 254 ms 26 ms bu-ether45.asbnva1611w-bcr00.tbone.rr.com [107.14.19.44]
7 565 ms 24 ms 141 ms 0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
8 70 ms 63 ms 270 ms 209.48.38.225
9 237 ms 171 ms 144 ms 209.48.42.54
10 587 ms 333 ms 45 ms 216.239.46.248
11 59 ms 110 ms 27 ms 72.14.236.98
12 222 ms 25 ms 43 ms 216.239.40.165
13 170 ms 24 ms 92 ms 209.85.252.243
14 29 ms 408 ms 39 ms 209.85.245.177
15 126 ms 329 ms 46 ms lga15s42-in-f8.1e100.net [74.125.226.8]
Trace complete.
The tracert makes me think that the problem is on Time Warner's end because the route up until the cable modem is always low. Thoughts? Suggestions?
I'm having a twc tech come out later today.