Highlighted
Participant

Could use Help with latency issues im having.

First off I apologize for the amount of txt there is and hope that it doesnt scare you off.

 

It all started for me around late may when my connection started fluxuating thru the month, then in mid June my father saw a TWC tech working on the Lines outside one of the neighboors house. After which my connection had finally gotten stable for about 2 weeks then fluxuated again, but it would be optimal during non peak hours such as 3am to 2pm depending on the days. When i would contact the tech reps for internet they would tell me they see no issues with my internet that everything was fine and i would try my best to explain why it wasnt fine and there is somekind of issue. Then i got a Tech to come out to my house scheduled 8am-12pm just to tell me that there doesnt seem to be anything wrong,telling me there didnt seem to be anything wrong on their equipment side also told me and i quote "i know some people do not want to hear this but it could be an issue sometime with customers equipment, maybe u have a virus or to many programs running that are chewing up your bandwidth", i replied with i understand what your saying but I have done many scans and troubleshooting as i could otherwise i would be calling you guys to find out whats wrong, he understood and again told me well there isnt any clear problem with the timewarner equipment.  But he did replace some parts in the box that were old and the wall mount also put a new coax from wall to cable modem/router. I told him to be sure Im going to be monitoring my connection to make sure the issue was just faulty cables and such. Unfortunatly when he was here and we tested everything it seemed to have worked and all was fine, he left and about an hour or two my latency would spike like it always after morning hours.

 

 

So far after he had gone and it started having issues again, i gave it till around 6pm to see if any changes would happens and become stable. Then I began trouble shooting as much as i could diconnecting devices from the network and re adding them one at a time to check for changes so far no good, then I focused on the only two computers I have on the network a Laptop(wireless) and Deckstop(ethernet) the other on it are a Android phone and Iphone. I disconnected both from the network and scanned them again with my protection softwares no threats detedcted form either. I was up to about 3am doing this when I speed test after the scans around 12am  there didnt seem to be any change, then around 3 i noticed that my latency when down to normal levels as did down and up, which gave me a good idea of when the good and bad hours would start then end. Also just incase to get a different opinion i downloaded AVG protection and using the free trial edition i did another scan on both computers which i left to finish while i slept. When i checked them my desktop had no threats, my laptop had some tracking cookies that avg caught but nothing else.

 

 

Ive made sure the os's and drivers on both computers are up to date. no change

Ive no way of knowing how to check if my nic is bad, but i dnt realy think that that could affect the speed of all the connected devices.

 

For my computers

desktop i used speedof.me TWC.com speed test speedtest.net and the speed test google has show up when u type speed test in search bar (tho it didnt appear when i did it for my laptop).

 

Laptop i used the same as desktop but google speed test

 

phone i used ookla speed test app and speedof.me on google chrome

 

iphone i do not have access to so i couldnt test but it has been discounnected the whole day with no change.

 

After all this im thinking possible issues is that the cables in my house maybe more damaged then what was replaced, or im being throttled, problems with my modem/router tho i have had it replced for the 3rd time, and possibly issues with how the neighborhood hub is connected to each house.

 

Ill be posting the Info from my modem/router also the trace routes/ pings i did for twc.com google.com youtube.com.

26 REPLIES 26
Participant

Re: Could use Help with latency issues im having.

The Cable modem/router i have is the one provided by Twc its called the Technicolor

 

WAN Network
Internet: Active
Local time: 2016_07_10 18:30:33
System Uptime: 0 days 02h:09m:19s
WAN IP Address (IPv4): 66.25.75.106
DHCP Client (IPv4): Enabled
DHCP Lease Expire Time (IPv4): 0d:11h:35m
WAN MAC: 70 5A 9E 50 EC C1
eMTA MAC: 70 5A 9E 50 EC C0
CM MAC: 70 5A 9E 50 EC BF
Host Name:
Domain Name:
Initialization Procedure
Initialize Hardware: Complete
Acquire Downstream Channel: Complete
Upstream Ranging: Complete
DHCP Bound: Complete
Set Time of Day: Complete
Configuration File Download: Complete
Registration: Complete
Cable Modem HW Version: Vendor: BOOT Version: Core Version: Model: Product Type: Flash Part: Download Version: Serial Number:
1.1
Technicolor
4.0.7_Technicolor
01.ED.04.29.00
TC8717T
Technicolor DOCSIS 3.0 Packet Cable 2.0 advanced cable gateway
128 MB
01.ED.04.29.00
CP1609DB5HG
Downstream Channel Bonding Value Index Lock Status Frequency SNR Power Modulation
12345678910111213141516
LockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLocked
531 MHz537 MHz543 MHz549 MHz555 MHz561 MHz567 MHz573 MHz579 MHz585 MHz591 MHz597 MHz603 MHz609 MHz615 MHz621 MHz
41.6 dB41.6 dB41.9 dB41.7 dB41.5 dB41.1 dB40.8 dB40.6 dB40.4 dB40.6 dB40.6 dB40.4 dB40.4 dB40.2 dB40.2 dB40.2 dB
4.3 dBmV4.4 dBmV4.6 dBmV4.7 dBmV4.5 dBmV4.1 dBmV3.8 dBmV3.6 dBmV3.7 dBmV3.8 dBmV3.8 dBmV3.9 dBmV3.8 dBmV3.7 dBmV3.8 dBmV3.7 dBmV
256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM
Upstream Channel Bonding Value Index Lock Status Frequency Symbol Rate Power Level Modulation Channel ID
1234
LockedLockedLockedLocked
24.2 MHz19.4 MHz30.6 MHz37.0 MHz
5120 Ksym/sec2560 Ksym/sec5120 Ksym/sec2560 Ksym/sec
42.3 dBmV42.3 dBmV42.3 dBmV43.8 dBmV
ATDMATDMAATDMAATDMA
6578
CM Error Codewords   Unerrored Codewords Correctable Codewords Uncorrectable Codewords
349974580348996218348996238348996257348996276348996296348996315348996334348996354348996373348996402348996334348996265348996197348996128348995972
0000000000000000
00000000
Participant

Re: Could use Help with latency issues im having.

Trace Route and Pings from Desktop

 

Tracing route to google.com [2607:f8b0:4008:80a::200e]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2605:6000:640a:7000:725a:9eff:fe50:ecc3
  2     *        *        *     Request timed out.
  3   340 ms   371 ms   426 ms  2605:6000:0:4::e:42e2
  4   313 ms   320 ms   301 ms  2605:6000:0:4::4:310
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7   369 ms   441 ms   441 ms  2610:18:113:d::1
  8   264 ms   304 ms   276 ms  2610:18:113:a::2
  9   332 ms   347 ms   373 ms  2001:4860:0:e01::3
 10   329 ms   351 ms   383 ms  2001:4860::8:0:2c9d
 11   385 ms   367 ms   340 ms  2001:4860::1:0:245b
 12     *        *        *     Request timed out.
 13   388 ms   358 ms   325 ms  mia07s34-in-x0e.1e100.net [2607:f8b0:4008:80a::200e]

Trace complete.

 

Pinging google.com [2607:f8b0:4008:80a::200e] with 32 bytes of data:
Reply from 2607:f8b0:4008:80a::200e: time=437ms
Reply from 2607:f8b0:4008:80a::200e: time=354ms
Reply from 2607:f8b0:4008:80a::200e: time=310ms
Reply from 2607:f8b0:4008:80a::200e: time=316ms

Ping statistics for 2607:f8b0:4008:80a::200e:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 310ms, Maximum = 437ms, Average = 354ms

 

Tracing route to youtube.com [2607:f8b0:4008:80a::200e]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2605:6000:640a:7000:725a:9eff:fe50:ecc3
  2     *        *        *     Request timed out.
  3   342 ms   296 ms   327 ms  2605:6000:0:4::e:42e2
  4   321 ms   331 ms   329 ms  2605:6000:0:4::4:310
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7   281 ms   331 ms   374 ms  2610:18:113:d::1
  8   452 ms   430 ms   431 ms  2610:18:113:a::2
  9   458 ms   386 ms   427 ms  2001:4860:0:e01::3
 10   469 ms   384 ms   400 ms  2001:4860::8:0:2c9d
 11   536 ms   562 ms   476 ms  2001:4860::1:0:245b
 12     *        *     1851 ms  2001:4860:0:1::50f
 13   533 ms   545 ms   558 ms  mia07s34-in-x0e.1e100.net [2607:f8b0:4008:80a::200e]

Trace complete.

 

Pinging youtube.com [2607:f8b0:4008:80a::200e] with 32 bytes of data:
Reply from 2607:f8b0:4008:80a::200e: time=392ms
Reply from 2607:f8b0:4008:80a::200e: time=291ms
Reply from 2607:f8b0:4008:80a::200e: time=308ms
Reply from 2607:f8b0:4008:80a::200e: time=275ms

Ping statistics for 2607:f8b0:4008:80a::200e:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 275ms, Maximum = 392ms, Average = 316ms

 

Tracing route to twc.com [71.74.183.9]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    10 ms    13 ms    11 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    30 ms    32 ms    32 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    12 ms    11 ms    13 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    16 ms    23 ms    25 ms  24.175.33.4
  6   221 ms   245 ms   222 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7   163 ms   178 ms   160 ms  bu-ether11.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.38]
  8    48 ms    46 ms    47 ms  bu-ether12.atlngamq46w-bcr00.tbone.rr.com [66.109.6.37]
  9    40 ms    36 ms    80 ms  bu-ether5.chrcnctr01w-bar01.tbone.rr.com [66.109.1.8]
 10    40 ms    38 ms    38 ms  24.161.238.58
 11    44 ms    42 ms    42 ms  71.74.183.9
 12    57 ms    39 ms    40 ms  71.74.183.9

Trace complete.

 

Pinging twc.com [71.74.183.9] with 32 bytes of data:
Reply from 71.74.183.9: bytes=32 time=45ms TTL=52
Reply from 71.74.183.9: bytes=32 time=43ms TTL=52
Reply from 71.74.183.9: bytes=32 time=44ms TTL=52
Reply from 71.74.183.9: bytes=32 time=47ms TTL=52

Ping statistics for 71.74.183.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 43ms, Maximum = 47ms, Average = 44ms

Participant

Re: Could use Help with latency issues im having.

Traceroute and pings from laptop

 

Pinging google.com [2607:f8b0:4000:801::200e] with 32 bytes of data:
Reply from 2607:f8b0:4000:801::200e: time=248ms
Reply from 2607:f8b0:4000:801::200e: time=180ms
Reply from 2607:f8b0:4000:801::200e: time=205ms
Reply from 2607:f8b0:4000:801::200e: time=190ms

Ping statistics for 2607:f8b0:4000:801::200e:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 180ms, Maximum = 248ms, Average = 205ms

 

Tracing route to google.com [2607:f8b0:4000:801::200e]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  2605:6000:640a:7000:725a:9eff:fe50:ecc3
  2     *        *        *     Request timed out.
  3   245 ms   195 ms   213 ms  2605:6000:0:4::e:43ea
  4   231 ms   224 ms   225 ms  2605:6000:0:4::4:310
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7   259 ms   285 ms   244 ms  2610:18:113:d::1
  8   365 ms   423 ms   373 ms  2610:18:113:a::2
  9   306 ms   286 ms   291 ms  2001:4860:0:e00::3
 10   289 ms   327 ms   328 ms  2001:4860:0:1::15d9
 11   326 ms   299 ms   258 ms  dfw25s08-in-x0e.1e100.net [2607:f8b0:4000:801::200e]

Trace complete.

 

Tracing route to youtube.com [2607:f8b0:4000:801::200e]
over a maximum of 30 hops:

  1     1 ms     5 ms     1 ms  2605:6000:640a:7000:725a:9eff:fe50:ecc3
  2     *        *        *     Request timed out.
  3   350 ms   379 ms   320 ms  2605:6000:0:4::e:43ea
  4   330 ms   313 ms   337 ms  2605:6000:0:4::4:310
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7   332 ms   322 ms   316 ms  2610:18:113:d::1
  8   307 ms   382 ms   343 ms  2610:18:113:a::2
  9   206 ms   264 ms   270 ms  2001:4860:0:e00::3
 10   255 ms   252 ms   268 ms  2001:4860:0:1::15d9
 11   146 ms   169 ms   155 ms  dfw25s08-in-x0e.1e100.net [2607:f8b0:4000:801::200e]

Trace complete.

 

Pinging youtube.com [2607:f8b0:4000:801::200e] with 32 bytes of data:
Reply from 2607:f8b0:4000:801::200e: time=246ms
Reply from 2607:f8b0:4000:801::200e: time=271ms
Reply from 2607:f8b0:4000:801::200e: time=205ms
Reply from 2607:f8b0:4000:801::200e: time=246ms

Ping statistics for 2607:f8b0:4000:801::200e:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 205ms, Maximum = 271ms, Average = 242ms

 

Tracing route to twc.com [71.74.189.86]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.0.1
  2    25 ms    19 ms    28 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    31 ms    32 ms    32 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    13 ms    28 ms    10 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    77 ms    64 ms    46 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6    74 ms    82 ms   100 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    43 ms    40 ms    53 ms  bu-ether7.enwdcocd02w-bar01.tbone.rr.com [66.109.1.53]
  8    34 ms    37 ms    37 ms  24.161.254.58
  9    38 ms    33 ms    30 ms  71.74.189.86
 10    36 ms    35 ms    37 ms  71.74.189.86

Trace complete.

 

Pinging twc.com [71.74.189.86] with 32 bytes of data:
Reply from 71.74.189.86: bytes=32 time=35ms TTL=54
Reply from 71.74.189.86: bytes=32 time=37ms TTL=54
Reply from 71.74.189.86: bytes=32 time=35ms TTL=54
Reply from 71.74.189.86: bytes=32 time=34ms TTL=54

Ping statistics for 71.74.189.86:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 37ms, Average = 35ms

 

Expert

Re: Could use Help with latency issues im having.

Turn off IPv6

 

Participant

Re: Could use Help with latency issues im having.

I did as you said and diasbled IPv6 in the router and just incase i disabled it in my adapter setting of my desktop and laptop. Ran another treart and ping got these results.

 

For Desktop

 


Pinging youtube.com [216.58.218.142] with 32 bytes of data:
Reply from 216.58.218.142: bytes=32 time=645ms TTL=54
Reply from 216.58.218.142: bytes=32 time=558ms TTL=54
Reply from 216.58.218.142: bytes=32 time=418ms TTL=54
Reply from 216.58.218.142: bytes=32 time=512ms TTL=54

Ping statistics for 216.58.218.142:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 418ms, Maximum = 645ms, Average = 533ms

 


Tracing route to youtube.com [216.58.218.142]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    17 ms    28 ms    74 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    29 ms    30 ms    31 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    17 ms    14 ms    15 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5   262 ms   301 ms   281 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6   216 ms   222 ms   240 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    21 ms    36 ms    22 ms  207.86.208.49
  8    66 ms    88 ms    69 ms  207.86.208.38
  9    66 ms     *       58 ms  108.170.240.67
 10   257 ms   268 ms   269 ms  72.14.234.143
 11   502 ms   544 ms   523 ms  dfw25s08-in-f142.1e100.net [216.58.218.142]

Trace complete.

 


Pinging twc.com [71.74.189.86] with 32 bytes of data:
Reply from 71.74.189.86: bytes=32 time=36ms TTL=54
Reply from 71.74.189.86: bytes=32 time=38ms TTL=54
Reply from 71.74.189.86: bytes=32 time=32ms TTL=54
Reply from 71.74.189.86: bytes=32 time=36ms TTL=54

Ping statistics for 71.74.189.86:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 38ms, Average = 35ms

 


Tracing route to twc.com [71.74.189.86]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms    17 ms    17 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    28 ms    32 ms    21 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    10 ms    21 ms    17 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5   323 ms   325 ms   322 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6   354 ms   328 ms   367 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    42 ms    41 ms    42 ms  bu-ether7.enwdcocd02w-bar01.tbone.rr.com [66.109.1.53]
  8    33 ms    33 ms    35 ms  24.161.254.58
  9    34 ms    34 ms    37 ms  71.74.189.86
 10    32 ms    32 ms    38 ms  71.74.189.86

Trace complete.

 


Pinging google.com [216.58.218.142] with 32 bytes of data:
Reply from 216.58.218.142: bytes=32 time=610ms TTL=54
Reply from 216.58.218.142: bytes=32 time=550ms TTL=54
Reply from 216.58.218.142: bytes=32 time=461ms TTL=54
Reply from 216.58.218.142: bytes=32 time=519ms TTL=54

Ping statistics for 216.58.218.142:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 461ms, Maximum = 610ms, Average = 535ms

 


Tracing route to google.com [216.58.218.142]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    14 ms    11 ms    13 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    39 ms    31 ms    20 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    12 ms    12 ms    16 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5   246 ms   218 ms   211 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6   381 ms   312 ms   279 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    21 ms    28 ms    18 ms  207.86.208.49
  8     *       55 ms    56 ms  207.86.208.38
  9    47 ms    44 ms    47 ms  108.170.240.67
 10   333 ms   292 ms   309 ms  72.14.234.143
 11   391 ms   485 ms   464 ms  dfw25s08-in-f142.1e100.net [216.58.218.142]

Trace complete.

 

For Laptop

 


Pinging google.com [216.58.218.142] with 32 bytes of data:
Reply from 216.58.218.142: bytes=32 time=168ms TTL=54
Reply from 216.58.218.142: bytes=32 time=244ms TTL=54
Reply from 216.58.218.142: bytes=32 time=296ms TTL=54
Reply from 216.58.218.142: bytes=32 time=244ms TTL=54

Ping statistics for 216.58.218.142:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 168ms, Maximum = 296ms, Average = 238ms

 


Tracing route to google.com [216.58.218.142]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  192.168.0.1
  2    26 ms    13 ms    26 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    27 ms    36 ms    37 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    19 ms    18 ms    20 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5   102 ms   106 ms   105 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6   262 ms   257 ms   255 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    24 ms    22 ms    22 ms  207.86.208.49
  8    68 ms    59 ms    65 ms  207.86.208.38
  9    54 ms    51 ms    54 ms  108.170.240.67
 10   336 ms   330 ms   289 ms  72.14.234.143
 11   600 ms   535 ms   451 ms  dfw25s08-in-f14.1e100.net [216.58.218.142]

Trace complete.

 

 


Pinging twc.com [71.74.183.9] with 32 bytes of data:
Reply from 71.74.183.9: bytes=32 time=46ms TTL=52
Reply from 71.74.183.9: bytes=32 time=50ms TTL=52
Reply from 71.74.183.9: bytes=32 time=42ms TTL=52
Reply from 71.74.183.9: bytes=32 time=73ms TTL=52

Ping statistics for 71.74.183.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 42ms, Maximum = 73ms, Average = 52ms

 


Tracing route to twc.com [71.74.183.9]
over a maximum of 30 hops:

  1     1 ms     1 ms     3 ms  192.168.0.1
  2    16 ms    14 ms    15 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    23 ms    97 ms    32 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    12 ms    10 ms    12 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    26 ms    23 ms    23 ms  24.175.33.4
  6   185 ms   178 ms   150 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7   235 ms   264 ms   294 ms  bu-ether11.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.38]
  8    47 ms    47 ms    48 ms  bu-ether12.atlngamq46w-bcr00.tbone.rr.com [66.109.6.37]
  9    38 ms    41 ms    39 ms  bu-ether5.chrcnctr01w-bar01.tbone.rr.com [66.109.1.8]
 10    44 ms    49 ms    40 ms  24.161.238.58
 11    44 ms    43 ms    40 ms  71.74.183.9
 12    55 ms    46 ms    51 ms  71.74.183.9

Trace complete.

 


Pinging youtube.com [216.58.218.142] with 32 bytes of data:
Reply from 216.58.218.142: bytes=32 time=147ms TTL=54
Reply from 216.58.218.142: bytes=32 time=167ms TTL=54
Reply from 216.58.218.142: bytes=32 time=193ms TTL=54
Reply from 216.58.218.142: bytes=32 time=157ms TTL=54

Ping statistics for 216.58.218.142:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 147ms, Maximum = 193ms, Average = 166ms

 


Tracing route to youtube.com [216.58.218.142]
over a maximum of 30 hops:

  1    11 ms     1 ms    <1 ms  192.168.0.1
  2    18 ms     8 ms    14 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    26 ms    22 ms    31 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    13 ms    18 ms    18 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5   184 ms   181 ms   160 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6   181 ms   160 ms   170 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    20 ms    22 ms    23 ms  207.86.208.49
  8    65 ms    70 ms    72 ms  207.86.208.38
  9    58 ms    67 ms    60 ms  108.170.240.67
 10   282 ms   273 ms   308 ms  72.14.234.143
 11   231 ms   287 ms   270 ms  dfw25s08-in-f14.1e100.net [216.58.218.142]

Trace complete.

Expert

Re: Could use Help with latency issues im having.

Is something running cloud, Itune sync, onedrive, dropbox? Something may be hoarding all the bandwidth.

This looks a little better with IPv6 off

 

Participant

Re: Could use Help with latency issues im having.

I dont use onedrive or dropbox, honestly have no idea what those are. My step mother is the only one with an iphone but i had it discconected from the modem/router all day yesterday with no change. At this hour of day while im typing this i did tracrt/ping tests and these are the results. I didnt include twc.com do to its not showing any difference compaired to google adn youtube.

 

From desktop

 

 

Pinging google.com [216.58.218.110] with 32 bytes of data:
Reply from 216.58.218.110: bytes=32 time=16ms TTL=52
Reply from 216.58.218.110: bytes=32 time=21ms TTL=52
Reply from 216.58.218.110: bytes=32 time=21ms TTL=52
Reply from 216.58.218.110: bytes=32 time=16ms TTL=52

Ping statistics for 216.58.218.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 21ms, Average = 18ms

 


Tracing route to google.com [216.58.194.142]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    15 ms    12 ms    12 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    29 ms    32 ms    32 ms  tge0-0-0.snantx5101h.texas.rr.com [24.28.133.233]
  4    12 ms    10 ms    11 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    22 ms    23 ms    24 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6    38 ms    32 ms    29 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    25 ms    18 ms    24 ms  207.86.208.49
  8    70 ms    69 ms    77 ms  207.86.208.38
  9    22 ms    20 ms    17 ms  108.170.240.65
 10    43 ms    41 ms    49 ms  209.85.250.83
 11    56 ms    59 ms    61 ms  dfw06s49-in-f14.1e100.net [216.58.194.142]

Trace complete.

 


Pinging youtube.com [216.58.218.110] with 32 bytes of data:
Reply from 216.58.218.110: bytes=32 time=30ms TTL=52
Reply from 216.58.218.110: bytes=32 time=18ms TTL=52
Reply from 216.58.218.110: bytes=32 time=23ms TTL=52
Reply from 216.58.218.110: bytes=32 time=22ms TTL=52

Ping statistics for 216.58.218.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 30ms, Average = 23ms

 


Tracing route to youtube.com [216.58.218.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    13 ms    13 ms    12 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    22 ms    32 ms    32 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4     8 ms    12 ms    13 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    30 ms    22 ms    23 ms  24.175.33.4
  6    28 ms    22 ms    23 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    15 ms    25 ms    19 ms  207.86.208.49
  8    71 ms    67 ms    70 ms  207.86.208.38
  9    75 ms    84 ms    67 ms  108.170.240.194
 10    17 ms    17 ms    25 ms  72.14.234.141
 11    19 ms    19 ms    22 ms  dfw25s07-in-f14.1e100.net [216.58.218.110]

Trace complete.

 

From laptop

 


Pinging google.com [216.58.218.110] with 32 bytes of data:
Reply from 216.58.218.110: bytes=32 time=21ms TTL=52
Reply from 216.58.218.110: bytes=32 time=18ms TTL=52
Reply from 216.58.218.110: bytes=32 time=62ms TTL=52
Reply from 216.58.218.110: bytes=32 time=21ms TTL=52

Ping statistics for 216.58.218.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 62ms, Average = 30ms

 


Tracing route to google.com [216.58.218.110]
over a maximum of 30 hops:

  1     1 ms     7 ms     1 ms  192.168.0.1
  2    19 ms    13 ms    16 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    29 ms    28 ms    27 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    11 ms    21 ms    16 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    35 ms    23 ms    23 ms  24.175.33.4
  6    29 ms    54 ms    24 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    23 ms    20 ms    23 ms  207.86.208.49
  8    68 ms    75 ms    67 ms  207.86.208.38
  9    73 ms    65 ms    69 ms  108.170.240.194
 10    23 ms    20 ms    22 ms  72.14.234.141
 11    21 ms    22 ms    20 ms  dfw25s07-in-f110.1e100.net [216.58.218.110]

Trace complete.

 


Pinging youtube.com [216.58.218.110] with 32 bytes of data:
Reply from 216.58.218.110: bytes=32 time=18ms TTL=52
Reply from 216.58.218.110: bytes=32 time=23ms TTL=52
Reply from 216.58.218.110: bytes=32 time=23ms TTL=52
Reply from 216.58.218.110: bytes=32 time=28ms TTL=52

Ping statistics for 216.58.218.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 28ms, Average = 23ms

 


Tracing route to youtube.com [216.58.218.110]
over a maximum of 30 hops:

  1     3 ms     7 ms     1 ms  192.168.0.1
  2    11 ms    12 ms    13 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    62 ms    25 ms    32 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    12 ms    26 ms    10 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    28 ms    29 ms    33 ms  24.175.33.4
  6    57 ms    44 ms    48 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    21 ms    18 ms    17 ms  207.86.208.49
  8    68 ms    66 ms    70 ms  207.86.208.38
  9    74 ms    97 ms    71 ms  108.170.240.194
 10    24 ms    21 ms    21 ms  72.14.234.141
 11    20 ms    19 ms    18 ms  dfw25s07-in-f110.1e100.net [216.58.218.110]

Trace complete.

 

Everything looks fine right? Well thats what it usually is at this time of day, I'll be posting the ones around 2 or 3pm when its usually isnt as good as this. Edit Also that i will post the system and event logs for today.

Participant

Re: Could use Help with latency issues im having.

Ok i have some good news and bad news. The good news the pings to google are great but the bad news is that the tracrts changed to how they were last night, and the fact i should of mentioned this earlier but i have the 100down and 10 up internet from twc because i play online games so latency is important to me and after i saw the changes in the ping test i opened up some games not at once but after checking my latency in them nothing has changed in that aspect.

 

Desktop

 


Pinging youtube.com [216.58.218.110] with 32 bytes of data:
Reply from 216.58.218.110: bytes=32 time=18ms TTL=52
Reply from 216.58.218.110: bytes=32 time=21ms TTL=52
Reply from 216.58.218.110: bytes=32 time=26ms TTL=52
Reply from 216.58.218.110: bytes=32 time=31ms TTL=52

Ping statistics for 216.58.218.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 31ms, Average = 24ms

 


Pinging google.com [216.58.218.110] with 32 bytes of data:
Reply from 216.58.218.110: bytes=32 time=25ms TTL=52
Reply from 216.58.218.110: bytes=32 time=18ms TTL=52
Reply from 216.58.218.110: bytes=32 time=23ms TTL=52
Reply from 216.58.218.110: bytes=32 time=17ms TTL=52

Ping statistics for 216.58.218.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 25ms, Average = 20ms

 


Tracing route to google.com [216.58.218.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    14 ms    15 ms    12 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    24 ms    40 ms    26 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    14 ms    15 ms    11 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    40 ms    39 ms    38 ms  24.175.33.4
  6   163 ms   183 ms   198 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    27 ms    20 ms    19 ms  207.86.208.49
  8    65 ms    56 ms    70 ms  207.86.208.38
  9   164 ms   163 ms   199 ms  108.170.240.194
 10    24 ms    43 ms    17 ms  72.14.234.141
 11    19 ms    24 ms    23 ms  dfw25s07-in-f110.1e100.net [216.58.218.110]

Trace complete.

 


Tracing route to youtube.com [216.58.218.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    20 ms    17 ms    13 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    33 ms    31 ms    29 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    12 ms    12 ms    15 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    34 ms    23 ms    31 ms  24.175.33.4
  6   174 ms   204 ms   209 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    25 ms    18 ms    22 ms  207.86.208.49
  8    91 ms    74 ms    75 ms  207.86.208.38
  9   204 ms   179 ms   189 ms  108.170.240.194
 10    26 ms    16 ms    33 ms  72.14.234.141
 11    28 ms    22 ms    25 ms  dfw25s07-in-f110.1e100.net [216.58.218.110]

Trace complete.

 

From laptop

 


Pinging google.com [216.58.218.110] with 32 bytes of data:
Reply from 216.58.218.110: bytes=32 time=30ms TTL=52
Reply from 216.58.218.110: bytes=32 time=20ms TTL=52
Reply from 216.58.218.110: bytes=32 time=29ms TTL=52
Reply from 216.58.218.110: bytes=32 time=21ms TTL=52

Ping statistics for 216.58.218.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 30ms, Average = 25ms

 


Tracing route to google.com [216.58.218.110]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.0.1
2 16 ms 16 ms 59 ms cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
3 47 ms 30 ms 23 ms tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
4 22 ms 29 ms 16 ms agg68.snantxvy01r.texas.rr.com [24.175.34.16]
5 23 ms 31 ms 23 ms 24.175.33.4
6 190 ms 275 ms 290 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
7 23 ms 21 ms 20 ms 207.86.208.49
8 69 ms 72 ms 77 ms 207.86.208.38
9 186 ms 195 ms 201 ms 108.170.240.194
10 23 ms 29 ms 25 ms 72.14.234.141
11 40 ms 24 ms 20 ms dfw25s07-in-f110.1e100.net [216.58.218.110]

Trace complete.

 


Pinging youtube.com [216.58.218.110] with 32 bytes of data:
Reply from 216.58.218.110: bytes=32 time=22ms TTL=52
Reply from 216.58.218.110: bytes=32 time=24ms TTL=52
Reply from 216.58.218.110: bytes=32 time=20ms TTL=52
Reply from 216.58.218.110: bytes=32 time=22ms TTL=52

Ping statistics for 216.58.218.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 24ms, Average = 22ms

 


Tracing route to youtube.com [216.58.218.110]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 15 ms 16 ms 18 ms cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
3 32 ms 31 ms 30 ms tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
4 11 ms 12 ms 10 ms agg68.snantxvy01r.texas.rr.com [24.175.34.16]
5 24 ms 23 ms 24 ms 24.175.33.4
6 177 ms 176 ms 188 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
7 24 ms 22 ms 20 ms 207.86.208.49
8 77 ms 73 ms 85 ms 207.86.208.38
9 247 ms 225 ms 206 ms 108.170.240.194
10 26 ms 22 ms 20 ms 72.14.234.141
11 19 ms 20 ms 25 ms dfw25s07-in-f110.1e100.net [216.58.218.110]

Trace complete.

 

 

Participant

Re: Could use Help with latency issues im having.

These are from doing test for the games im playing

 

World of Warcraft

 

from desktop

 

TRACEROUTE:
traceroute to 66.25.75.106 (66.25.75.106), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.867 ms  0.899 ms  0.954 ms
 2  * * *
 3  37.244.1.102 (37.244.1.102)  2.569 ms  2.756 ms  2.796 ms
 4  37.244.1.34 (37.244.1.34)  2.349 ms  2.446 ms  2.511 ms
 5  66.109.9.148 (66.109.9.148)  24.468 ms  24.514 ms  24.522 ms
 6  107.14.17.197 (107.14.17.197)  29.118 ms  27.730 ms  27.724 ms
 7  bu-ether11.chctilwc00w-bcr00.tbone.rr.com (66.109.6.21)  32.233 ms  31.371 ms  31.344 ms
 8  bu-ether23.dllstx976iw-bcr00.tbone.rr.com (66.109.9.41)  26.257 ms  26.256 ms  26.088 ms
 9  agg1.dllatxl301r.texas.rr.com (66.109.6.89)  32.840 ms  27.115 ms  27.156 ms
10  agg1.snantxvy01r.texas.rr.com (24.175.32.147)  32.307 ms  32.296 ms  32.550 ms
11  agg1.snantx5101h.texas.rr.com (24.175.34.17)  51.620 ms  51.424 ms  51.410 ms
12  tge6-1.snantx5101m.satx.rr.com (24.28.135.98)  35.150 ms  34.491 ms  34.513 ms
13  * * *
14  * * *
15  * * *


11/07/2016 19:47:14 UTC
--------------------

TRACEROUTE:
traceroute to 66.25.75.106 (66.25.75.106), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  1.821 ms  1.845 ms  1.896 ms
 2  * * *
 3  37.244.1.102 (37.244.1.102)  2.800 ms  2.968 ms  3.069 ms
 4  37.244.1.34 (37.244.1.34)  2.544 ms  2.675 ms  2.741 ms
 5  66.109.9.148 (66.109.9.148)  24.466 ms  24.504 ms  24.512 ms
 6  107.14.17.197 (107.14.17.197)  29.066 ms  26.725 ms  26.715 ms
 7  bu-ether11.chctilwc00w-bcr00.tbone.rr.com (66.109.6.21)  31.245 ms  31.210 ms  30.981 ms
 8  bu-ether23.dllstx976iw-bcr00.tbone.rr.com (66.109.9.41)  29.786 ms  29.794 ms  29.665 ms
 9  agg1.dllatxl301r.texas.rr.com (66.109.6.89)  32.504 ms  27.188 ms  27.173 ms
10  agg1.snantxvy01r.texas.rr.com (24.175.32.147)  32.314 ms  32.589 ms  32.621 ms
11  agg1.snantx5101h.texas.rr.com (24.175.34.17)  51.386 ms  47.880 ms  47.877 ms
12  tge6-1.snantx5101m.satx.rr.com (24.28.135.98)  34.675 ms  34.604 ms  34.623 ms
13  * * *
14  * * *
15  * * *


11/07/2016 19:47:14 UTC
--------------------

TRACEROUTE:
traceroute to 66.25.75.106 (66.25.75.106), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.423 ms  0.451 ms  0.568 ms
 2  * * *
 3  37.244.0.102 (37.244.0.102)  1.724 ms  1.740 ms  1.786 ms
 4  37.244.0.34 (37.244.0.34)  1.561 ms  1.578 ms  1.591 ms
 5  ge-11-0-2.pr0.dca20.tbone.rr.com (66.109.9.160)  10.697 ms  10.717 ms  10.721 ms
 6  66.109.1.216 (66.109.1.216)  34.987 ms  37.346 ms  37.383 ms
 7  bu-ether16.dllstx976iw-bcr00.tbone.rr.com (66.109.6.1)  42.078 ms  42.030 ms  42.089 ms
 8  agg1.dllatxl301r.texas.rr.com (66.109.6.89)  37.131 ms  37.016 ms  36.993 ms
 9  agg1.snantxvy01r.texas.rr.com (24.175.32.147)  43.552 ms  43.665 ms  43.668 ms
10  agg1.snantx5101h.texas.rr.com (24.175.34.17)  64.726 ms  53.580 ms  49.834 ms
11  tge6-1.snantx5101m.satx.rr.com (24.28.135.98)  43.467 ms  43.461 ms  43.495 ms
12  * * *
13  * * *
14  * * *
15  * * *


11/07/2016 19:47:14 UTC
--------------------

TRACEROUTE:
traceroute to 66.25.75.106 (66.25.75.106), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.296 ms  0.392 ms  0.545 ms
 2  * * *
 3  37.244.0.102 (37.244.0.102)  1.749 ms  1.776 ms  1.794 ms
 4  37.244.0.34 (37.244.0.34)  1.568 ms  1.589 ms  1.735 ms
 5  ge-11-0-2.pr0.dca20.tbone.rr.com (66.109.9.160)  10.721 ms  10.743 ms  10.755 ms
 6  66.109.1.216 (66.109.1.216)  36.694 ms  35.650 ms  35.609 ms
 7  bu-ether16.dllstx976iw-bcr00.tbone.rr.com (66.109.6.1)  40.162 ms  39.589 ms  39.589 ms
 8  agg1.dllatxl301r.texas.rr.com (66.109.6.89)  42.748 ms  42.761 ms  42.708 ms
 9  agg1.snantxvy01r.texas.rr.com (24.175.32.147)  43.533 ms  43.729 ms  43.727 ms
10  agg1.snantx5101h.texas.rr.com (24.175.34.17)  57.753 ms  53.695 ms  53.696 ms
11  tge6-1.snantx5101m.satx.rr.com (24.28.135.98)  42.928 ms  42.835 ms  42.878 ms
12  * * *
13  * * *
14  * * *
15  * * *


11/07/2016 19:47:16 UTC
--------------------

PING:
PING 66.25.75.106 (66.25.75.106) 56(84) bytes of data.

--- 66.25.75.106 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4998ms



11/07/2016 19:47:14 UTC
--------------------

PING:
PING 66.25.75.106 (66.25.75.106) 56(84) bytes of data.

--- 66.25.75.106 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4998ms



11/07/2016 19:47:14 UTC
--------------------

PING:
PING 66.25.75.106 (66.25.75.106) 56(84) bytes of data.

--- 66.25.75.106 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 5005ms



11/07/2016 19:47:16 UTC
--------------------

PING:
PING 66.25.75.106 (66.25.75.106) 56(84) bytes of data.

--- 66.25.75.106 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4998ms



11/07/2016 19:47:19 UTC
--------------------

MTR:
HOST: Blizzard                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                             0.0%    10    0.6   0.6   0.5   0.8   0.1
  2. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 37.244.1.102                               0.0%    10    3.9   2.7   2.3   3.9   0.4
  4. 37.244.1.34                                0.0%    10    2.3   2.6   2.3   3.7   0.6
  5. 66.109.9.148                               0.0%    10   26.4  24.7  24.5  26.4   0.6
  6. 107.14.17.197                              0.0%    10   27.9  28.2  26.6  30.0   1.0
  7. bu-ether11.chctilwc00w-bcr00.tbone.rr.com  0.0%    10   33.5  29.7  26.7  33.5   2.4
  8. bu-ether23.dllstx976iw-bcr00.tbone.rr.com  0.0%    10   29.9  28.2  26.5  30.0   1.2
  9. agg1.dllatxl301r.texas.rr.com              0.0%    10   29.9  31.3  27.9  34.3   2.0
 10. agg1.snantxvy01r.texas.rr.com              0.0%    10   32.2  32.3  32.1  32.6   0.2
 11. agg1.snantx5101h.texas.rr.com              0.0%    10   44.7  46.7  42.7  54.2   4.3
 12. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


11/07/2016 19:47:14 UTC
--------------------

MTR:
HOST: Blizzard               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                0.0%    10    0.9   0.5   0.3   0.9   0.2
  2. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 37.244.0.102                               0.0%    10    1.8   1.7   1.7   1.8   0.0
  4. 37.244.0.34                                0.0%    10    1.5   1.9   1.5   3.2   0.6
  5. ge-11-0-2.pr0.dca20.tbone.rr.com           0.0%    10   10.7  10.8  10.7  11.0   0.1
  6. 66.109.1.216                               0.0%    10   36.4  36.7  34.8  38.2   1.2
  7. bu-ether16.dllstx976iw-bcr00.tbone.rr.com  0.0%    10   42.0  37.8  35.1  42.0   2.3
  8. agg1.dllatxl301r.texas.rr.com              0.0%    10   42.2  38.7  36.1  43.2   2.7
  9. agg1.snantxvy01r.texas.rr.com              0.0%    10   43.6  43.7  43.5  43.8   0.1
 10. agg1.snantx5101h.texas.rr.com              0.0%    10   63.2  63.3  54.5 101.3  14.3
 11. tge6-1.snantx5101m.satx.rr.com             0.0%    10   42.7  43.0  42.6  43.4   0.3
 12. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


11/07/2016 19:47:14 UTC
--------------------

MTR:
HOST: Blizzard                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                             0.0%    10    0.7   0.7   0.4   1.4   0.3
  2. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 37.244.1.102                               0.0%    10    2.6   2.9   2.5   4.8   0.7
  4. 37.244.1.34                                0.0%    10    2.4   2.5   2.4   2.8   0.1
  5. 66.109.9.148                               0.0%    10   24.5  24.5  24.4  24.6   0.0
  6. 107.14.17.197                              0.0%    10   28.0  28.1  26.6  29.8   1.1
  7. bu-ether11.chctilwc00w-bcr00.tbone.rr.com  0.0%    10   28.9  30.6  26.8  33.2   2.1
  8. bu-ether23.dllstx976iw-bcr00.tbone.rr.com  0.0%    10   28.6  28.2  26.3  29.9   1.2
  9. agg1.dllatxl301r.texas.rr.com              0.0%    10   31.8  31.7  27.8  34.4   2.5
 10. agg1.snantxvy01r.texas.rr.com              0.0%    10   32.4  32.2  32.1  32.4   0.1
 11. agg1.snantx5101h.texas.rr.com              0.0%    10   48.1  49.4  42.8  65.3   6.5
 12. tge6-1.snantx5101m.satx.rr.com             0.0%    10   35.0  36.5  34.4  46.1   3.5
 13. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


11/07/2016 19:47:14 UTC
--------------------

MTR:
HOST: Blizzard               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                0.0%    10    0.4   0.4   0.3   0.6   0.1
  2. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 37.244.0.102                               0.0%    10    1.6   1.7   1.6   2.1   0.2
  4. 37.244.0.34                                0.0%    10    1.6   1.6   1.5   1.8   0.1
  5. ge-11-0-2.pr0.dca20.tbone.rr.com           0.0%    10   10.7  10.7  10.7  10.9   0.1
  6. 66.109.1.216                               0.0%    10   38.6  36.4  34.6  38.6   1.4
  7. bu-ether16.dllstx976iw-bcr00.tbone.rr.com  0.0%    10   40.0  37.4  34.3  41.3   2.6
  8. agg1.dllatxl301r.texas.rr.com              0.0%    10   40.2  39.3  36.0  42.2   2.2
  9. agg1.snantxvy01r.texas.rr.com              0.0%    10   43.5  43.6  43.5  43.8   0.1
 10. agg1.snantx5101h.texas.rr.com              0.0%    10   53.7  58.6  53.5  63.6   3.4
 11. tge6-1.snantx5101m.satx.rr.com            80.0%    10   43.3  43.2  43.2  43.3   0.0
 12. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


11/07/2016 19:47:16 UTC
--------------------