Participant

Re: Could use Help with latency issues im having.

from laptop

 

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 5006ms



11/07/2016 19:33:43 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 5003ms



11/07/2016 19:33:43 UTC
--------------------

TRACEROUTE:
traceroute to 66.25.75.106 (66.25.75.106), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.441 ms  0.567 ms  0.680 ms
 2  * * *
 3  37.244.1.102 (37.244.1.102)  2.537 ms  2.548 ms  2.596 ms
 4  37.244.1.34 (37.244.1.34)  2.411 ms  2.441 ms  2.443 ms
 5  66.109.9.148 (66.109.9.148)  24.482 ms  24.519 ms  24.523 ms
 6  107.14.17.197 (107.14.17.197)  29.494 ms  28.578 ms  28.583 ms
 7  bu-ether11.chctilwc00w-bcr00.tbone.rr.com (66.109.6.21)  32.838 ms  31.398 ms  31.407 ms
 8  bu-ether23.dllstx976iw-bcr00.tbone.rr.com (66.109.9.41)  28.596 ms  28.609 ms  28.621 ms
 9  agg1.dllatxl301r.texas.rr.com (66.109.6.89)  32.550 ms  35.294 ms  35.323 ms
10  agg1.snantxvy01r.texas.rr.com (24.175.32.147)  38.726 ms  39.273 ms  39.306 ms
11  agg1.snantx5101h.texas.rr.com (24.175.34.17)  51.540 ms  60.959 ms  60.982 ms
12  tge6-1.snantx5101m.satx.rr.com (24.28.135.98)  38.726 ms  38.000 ms  38.032 ms
13  * * *
14  * * *
15  * * *


11/07/2016 19:33:43 UTC
--------------------

TRACEROUTE:
traceroute to 66.25.75.106 (66.25.75.106), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.445 ms  0.566 ms  0.683 ms
 2  * * *
 3  37.244.1.102 (37.244.1.102)  2.603 ms  2.660 ms  2.730 ms
 4  37.244.1.34 (37.244.1.34)  2.414 ms  2.443 ms  2.514 ms
 5  66.109.9.148 (66.109.9.148)  24.508 ms  24.560 ms  24.563 ms
 6  107.14.17.197 (107.14.17.197)  27.315 ms  30.908 ms  30.899 ms
 7  bu-ether11.chctilwc00w-bcr00.tbone.rr.com (66.109.6.21)  34.865 ms  33.603 ms  33.550 ms
 8  bu-ether23.dllstx976iw-bcr00.tbone.rr.com (66.109.9.41)  30.879 ms  30.814 ms  30.786 ms
 9  agg1.dllatxl301r.texas.rr.com (66.109.6.89)  34.475 ms  29.667 ms  29.660 ms
10  agg1.snantxvy01r.texas.rr.com (24.175.32.147)  38.979 ms  38.691 ms  38.852 ms
11  agg1.snantx5101h.texas.rr.com (24.175.34.17)  59.888 ms  58.546 ms  58.530 ms
12  tge6-1.snantx5101m.satx.rr.com (24.28.135.98)  38.812 ms  39.170 ms  39.194 ms
13  * * *
14  * * *
15  * * *


11/07/2016 19:33:43 UTC
--------------------

TRACEROUTE:
traceroute to 66.25.75.106 (66.25.75.106), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.452 ms  0.529 ms  0.631 ms
 2  * * *
 3  37.244.0.102 (37.244.0.102)  1.629 ms  1.658 ms  1.778 ms
 4  37.244.0.34 (37.244.0.34)  1.786 ms  1.860 ms  1.991 ms
 5  ge-11-0-2.pr0.dca20.tbone.rr.com (66.109.9.160)  10.705 ms  10.726 ms  10.732 ms
 6  66.109.1.216 (66.109.1.216)  35.495 ms  37.899 ms  37.934 ms
 7  bu-ether16.dllstx976iw-bcr00.tbone.rr.com (66.109.6.1)  38.011 ms  37.922 ms  37.914 ms
 8  agg1.dllatxl301r.texas.rr.com (66.109.6.89)  37.387 ms  37.389 ms  37.312 ms
 9  agg1.snantxvy01r.texas.rr.com (24.175.32.147)  43.525 ms  43.712 ms  43.728 ms
10  agg1.snantx5101h.texas.rr.com (24.175.34.17)  53.667 ms  53.774 ms  52.297 ms
11  tge6-1.snantx5101m.satx.rr.com (24.28.135.98)  42.970 ms  42.984 ms  42.858 ms
12  * * *
13  * * *
14  * * *
15  * * *


11/07/2016 19:33:48 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:33:48 UTC
--------------------

TRACEROUTE:
traceroute to 66.25.75.106 (66.25.75.106), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.412 ms  0.450 ms  0.552 ms
 2  * * *
 3  37.244.0.102 (37.244.0.102)  1.902 ms  1.921 ms  1.928 ms
 4  37.244.0.34 (37.244.0.34)  1.429 ms  1.451 ms  1.477 ms
 5  ge-11-0-2.pr0.dca20.tbone.rr.com (66.109.9.160)  10.749 ms  10.771 ms  10.778 ms
 6  66.109.1.216 (66.109.1.216)  38.683 ms  37.500 ms  37.511 ms
 7  bu-ether16.dllstx976iw-bcr00.tbone.rr.com (66.109.6.1)  41.367 ms  41.122 ms  41.112 ms
 8  agg1.dllatxl301r.texas.rr.com (66.109.6.89)  40.834 ms  40.401 ms  40.389 ms
 9  agg1.snantxvy01r.texas.rr.com (24.175.32.147)  44.037 ms  43.669 ms  43.665 ms
10  agg1.snantx5101h.texas.rr.com (24.175.34.17)  63.629 ms  56.398 ms  56.411 ms
11  tge6-1.snantx5101m.satx.rr.com (24.28.135.98)  43.579 ms * *
12  * * *
13  * * *
14  * * *
15  * * *


11/07/2016 19:33:50 UTC
--------------------

MTR:
HOST: Blizzard                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                             0.0%    10    0.5   0.5   0.4   0.7   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   3.2   2.6   5.0   0.8
  4. 37.244.1.34                                0.0%    10    2.6   2.7   2.4   3.8   0.5
  5. 66.109.9.148                               0.0%    10   24.5  25.0  24.5  28.7   1.3
  6. 107.14.17.197                              0.0%    10   36.7  32.3  26.5  36.7   3.7
  7. bu-ether11.chctilwc00w-bcr00.tbone.rr.com  0.0%    10   40.7  35.7  30.7  41.1   4.0
  8. bu-ether23.dllstx976iw-bcr00.tbone.rr.com  0.0%    10   35.7  32.7  28.9  36.6   2.9
  9. agg1.dllatxl301r.texas.rr.com              0.0%    10   42.6  36.7  31.9  43.9   4.6
 10. agg1.snantxvy01r.texas.rr.com              0.0%    10   34.3  36.2  32.2  41.8   3.2
 11. agg1.snantx5101h.texas.rr.com              0.0%    10   51.8  52.9  45.2  58.6   4.3
 12. tge6-1.snantx5101m.satx.rr.com            50.0%    10   43.2  42.9  38.6  51.0   4.9
 13. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


11/07/2016 19:33:43 UTC
--------------------

MTR:
HOST: Blizzard                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                             0.0%    10    0.6   0.5   0.4   0.6   0.1
  2. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 37.244.1.102                               0.0%    10    2.5   2.9   2.5   3.8   0.5
  4. 37.244.1.34                                0.0%    10    2.6   2.5   2.3   2.6   0.1
  5. 66.109.9.148                               0.0%    10   24.5  24.9  24.5  28.7   1.3
  6. 107.14.17.197                              0.0%    10   36.8  32.3  26.5  36.8   3.7
  7. bu-ether11.chctilwc00w-bcr00.tbone.rr.com  0.0%    10   40.8  36.1  30.8  41.1   3.8
  8. bu-ether23.dllstx976iw-bcr00.tbone.rr.com  0.0%    10   35.8  32.3  28.9  36.6   2.8
  9. agg1.dllatxl301r.texas.rr.com              0.0%    10   42.6  36.4  31.6  43.9   4.8
 10. agg1.snantxvy01r.texas.rr.com              0.0%    10   34.1  36.3  32.1  41.8   3.2
 11. agg1.snantx5101h.texas.rr.com              0.0%    10   51.8  52.3  45.2  58.6   3.9
 12. tge6-1.snantx5101m.satx.rr.com            50.0%    10   42.1  42.6  35.6  51.9   6.0
 13. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


11/07/2016 19:33:43 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 5003ms



11/07/2016 19:33:53 UTC
--------------------

MTR:
HOST: Blizzard               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                0.0%    10    0.5   0.5   0.3   1.2   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.7   2.0   1.7   2.5   0.3
  4. 37.244.0.34                                0.0%    10    1.5   1.8   1.5   2.8   0.4
  5. ge-11-0-2.pr0.dca20.tbone.rr.com           0.0%    10   10.8  14.4  10.7  45.6  11.0
  6. 66.109.1.216                               0.0%    10   39.1  42.5  35.4  47.0   3.6
  7. bu-ether16.dllstx976iw-bcr00.tbone.rr.com  0.0%    10   39.7  43.0  39.5  49.3   3.5
  8. agg1.dllatxl301r.texas.rr.com              0.0%    10   44.9  45.5  37.4  50.4   3.9
  9. agg1.snantxvy01r.texas.rr.com              0.0%    10   44.0  48.9  43.8  54.7   4.3
 10. agg1.snantx5101h.texas.rr.com              0.0%    10   55.0  74.6  53.7 128.5  27.3
 11. tge6-1.snantx5101m.satx.rr.com             0.0%    10   45.4  52.9  45.4  84.5  11.3
 12. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


11/07/2016 19:33:48 UTC
--------------------

MTR:
HOST: Blizzard               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                0.0%    10    0.3   0.4   0.3   0.5   0.1
  2. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 37.244.0.102                               0.0%    10    2.1   1.9   1.7   2.3   0.3
  4. 37.244.0.34                                0.0%    10    1.6   1.8   1.5   3.2   0.5
  5. ge-11-0-2.pr0.dca20.tbone.rr.com           0.0%    10   10.8  10.7  10.7  10.8   0.0
  6. 66.109.1.216                               0.0%    10   36.4  41.8  36.4  46.5   4.1
  7. bu-ether16.dllstx976iw-bcr00.tbone.rr.com  0.0%    10   40.3  43.8  38.2  47.8   3.3
  8. agg1.dllatxl301r.texas.rr.com              0.0%    10   38.5  44.8  38.5  49.6   3.5
  9. agg1.snantxvy01r.texas.rr.com              0.0%    10   45.7  49.0  43.7  52.7   3.0
 10. agg1.snantx5101h.texas.rr.com              0.0%    10   63.8  65.2  60.4  69.0   3.0
 11. tge6-1.snantx5101m.satx.rr.com            80.0%    10   43.2  46.8  43.2  50.3   5.0
 12. ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


11/07/2016 19:33:48 UTC
--------------------

 

 

 

Participant

Re: Could use Help with latency issues im having.

League of legends

 

from desktop

 


Tracing route to 192.64.170.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms    12 ms    26 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    23 ms    21 ms    28 ms  tge0-0-0.snantx5101h.texas.rr.com [24.28.133.233]
  4    14 ms    12 ms    11 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5   182 ms   190 ms   168 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6   258 ms   196 ms   187 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    28 ms    37 ms    20 ms  0.ae4.pr1.dfw10.tbone.rr.com [107.14.19.97]
  8    17 ms    27 ms    24 ms  24.27.236.233
  9   269 ms   253 ms   224 ms  104.160.134.35
 10    37 ms    42 ms    74 ms  ae35-br02.chi01.riotdirect.net [104.160.159.24]
 11    42 ms    40 ms    43 ms  104.160.131.36
 12   310 ms   238 ms    56 ms  104.160.131.44
 13    41 ms    37 ms    41 ms  104.160.131.103
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.

 30     *        *        *     Request timed out.

 

 


Pinging 192.64.170.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.64.170.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

from laptop

 


Pinging 192.64.170.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.64.170.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 


Pinging 192.64.170.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.64.170.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

 

Event logs from router/modem

 

All Logs for Today

 Time  Priority  ID  Text  Endpoint 
2016-07-11 02:49:455-Information2147483647Provisioning Complete24.93.40.100
2016-07-11 02:47:175-Information2147483647MTA RESET:CM:0;MTA Reset due to CM_RESET30.8.67.134
2016-07-11 02:47:115-Information2147483647DOCSIS-CONN-ERROR;CM not operational

65.24.1.101

 

 

 

System logs from router/modem

 

All Logs for Today

 Time  Priority  Description 
Mon Jul 11 13:28:28 2016Critical (3) Http login:admin from IP address 192.168.0.3

 

 

In my opionion it seems realy sketchy to me that after going to the forums about this issue of mine that my connection to google and youtube would inprove so much in a night. It probably me just being paranoid but trying to fix this is stressing me out a fair amount. Also sorry it took me awhile to post it when i said 2 was having time out when getting tracrt/ ping for league of legend servers did 5 test for both got same results each time and having to gett this all to fit into multiple post.

Participant

Re: Could use Help with latency issues im having.

http://n1.netalyzr.icsi.berkeley.edu/summary/id=369839a0-6944-5c7d0e61-5921-45eb-8726

 

I recently did this test if that helps at all

 

waited 30min did this one

 

 http://n1.netalyzr.icsi.berkeley.edu/summary/id=369839a0-6944-dbd93fce-5016-4761-b5e5

 

gonna add some screen shots i did of speed test from twc compared to speedof.me theres time stamps in the tab titles. No one in my house uses the internet that would cause it to drop like that in the house.

 

http://puu.sh/pYuGl/89c1b50695.jpg

http://puu.sh/pYuNb/c972dda299.png

http://puu.sh/pYvsz/bfd547159c.png

http://puu.sh/pYvxY/65de8f69f4.png

Participant

Re: Could use Help with latency issues im having.

http://n2.netalyzr.icsi.berkeley.edu/summary/id=36a470be-17674-516bb217-84f1-4cf8-a2c0

 

these i did just now

 

http://puu.sh/pYwjp/7851e160b2.png

http://puu.sh/pYwjV/36fb287a27.png

 


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

  1     2 ms    <1 ms    <1 ms  192.168.0.1
  2    15 ms    14 ms    19 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    30 ms    93 ms    30 ms  tge0-0-0.snantx5101h.texas.rr.com [24.28.133.233]
  4    12 ms    17 ms     5 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    26 ms    22 ms    23 ms  24.175.33.4
  6   347 ms   371 ms   391 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7   253 ms   232 ms   232 ms  bu-ether12.tustca4200w-bcr00.tbone.rr.com [66.109.6.0]
  8    55 ms    54 ms    75 ms  0.ae3.pr1.lax10.tbone.rr.com [107.14.19.56]
  9   178 ms   194 ms   181 ms  107.14.17.215
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   354 ms   313 ms   313 ms  205.251.232.165
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 


Pinging google.com.com [52.33.196.199] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 52.33.196.199:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Highlighted
Expert

Re: Could use Help with latency issues im having.

Is this 30/5 or 50/5?

 

 

What speed do you pay for? The UPLOAD looks horrible

 

Expert

Re: Could use Help with latency issues im having.

The other thing i'd do is change the DHCP start from 192.168.0.2 to 192.168.0.100

 Some devices have an issue with x.x.x.2 to x.x.x.10

 

 next issue is why this happened: Did you call TWC?

 

2016-07-11 02:49:455-Information2147483647Provisioning Complete24.93.40.100

 and then there's this:

  5   182 ms   190 ms   168 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146]
  6   258 ms   196 ms   187 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7    28 ms    37 ms    20 ms  0.ae4.pr1.dfw10.tbone.rr.com [107.14.19.97]
  8    17 ms    27 ms    24 ms  24.27.236.233
  9   269 ms   253 ms   224 ms  104.160.134.35
 10    37 ms    42 ms    74 ms  ae35-br02.chi01.riotdirect.net [104.160.159.24]
 11    42 ms    40 ms    43 ms  104.160.131.36
 12   310 ms   238 ms    56 ms  104.160.131.44

Participant

Re: Could use Help with latency issues im having.

I pay for 100 down 10 up and ive been having this problem for weeks now with no solution. Its hard sometimes to catch that drop in speed. Makes it hard for me to trust the speed test from what they tell me and what i see when im ingame which is usually around the 60ms but after 2pm spikes to 350-400ms or how my videos load on youtube i used to be able to load at 720p no problem then i had to decrease it down to 360p. Around 9:11pm today my latency had a significant decrease.to my normal levels as is in the morning hours. While i was ingame and im still checking it every few miniutes to see if itll rise and not go down as it usually does. So far no increase staying at a steady 57ms. Dont know how cuz i havnt done anything to any device in my house since my last post.

 

I have called TWC multiple times trying to have this fixed and they would always tell em they see nothing wrong, then a tech came out and replaced some parts in my box and a wall mount and coax cable for my modem/router. he also told me there doesnt seem to be any issues but after he left like usual after 2pm its spiked and stayed till next morning hours.he also told me he was the 3rd tech to come to my neighboorhood.

 

I just checked its at 192.168.0.2 starting 192.168.0.254 ending, i havent changed this at all.

Participant

Re: Could use Help with latency issues im having.

So when i saw the significant drop from 350ms to 60 ms which is my norm last night I was foolish to think maybe something happened and the issue was gone well around 3pm i had this.

 

 

http://puu.sh/pZrGi/9c4eed9c41.png

 

http://puu.sh/pZruV/371e95e350.png

 


Pinging google.com.com [54.201.82.69] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 54.201.82.69:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 


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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    23 ms    15 ms    16 ms  cpe-66-25-64-1.satx.res.rr.com [66.25.64.1]
  3    33 ms    22 ms    33 ms  tge0-0-1.snantx5101h.texas.rr.com [24.28.135.97]
  4    13 ms    20 ms    11 ms  agg68.snantxvy01r.texas.rr.com [24.175.34.16]
  5    22 ms    24 ms    23 ms  24.175.33.4
  6   186 ms   171 ms   178 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
  7   259 ms   277 ms   325 ms  bu-ether12.tustca4200w-bcr00.tbone.rr.com [66.109.6.0]
  8   188 ms   194 ms   210 ms  0.ae2.pr1.lax10.tbone.rr.com [107.14.19.54]
  9   170 ms   200 ms   207 ms  107.14.17.215
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17    82 ms    87 ms    83 ms  205.251.232.167
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 

Again there is no machince on my netwrok that consumes enough banmdwidth to drop a 100down 10up  connection like this.

Participant

Re: Could use Help with latency issues im having.

Forgot to add Todays logs on my modem/router

 

Event Logs

 

All Logs for Today

 Time  Priority  ID  Text  Endpoint 
2016-07-12 02:49:455-Information35MTA Last 24 Hours: Count of No ACK rec'd from Call Agent=024.93.40.100
2016-07-12 02:49:455-Information35MTA Last 24 Hours: Average Latency for Response to MGCP Messages=0 ms24.93.40.100
2016-07-12 02:49:455-Information35MTA Last 24 Hours: Average Latency via RTCP Packets=0 ms24.93.40.100
2016-07-12 02:49:455-Information35MTA Last 24 Hours: Maximum Jitter Measurements=024.93.40.100
2016-07-12 02:49:455-Information35MTA Last 24 Hours: Average Jitter Measurements=024.93.40.100

 

System Logs

 

All Logs for Today

 Time  Priority  Description 
Tue Jul 12 14:13:38 2016Critical (3) Http login:admin from IP address 192.168.0.3

 

 

Edit: around 4:20pm i saw a drop in my latency when i was ingame back to normal value of 60ms but no change in the speed tests from google or twc. I wish i had more knowledge in networking to understand why this is happening.

 

http://puu.sh/pZvwr/034610d610.png

http://puu.sh/pZvA2/aee875458b.png

 

Edit at 4:45pm i left my house to go to the stor with my dad came back at around 5:18pm saw my latency had spiked to 175ms ingame. No changes from google speed test but twc speed test say improved speeds,

 

http://puu.sh/pZzq0/a7650c0649.png

http://puu.sh/pZzqy/736cbe08a1.png

 

Edit: 5:53pm Ingame latency had drop to normal 60ms while little to no changes in google speed test compared to lat check twc speeds test had shown decrease in down and up again. Compared to how its been the last weeks the way the internet is acting has shows slight imporvement but speed test from twc and google are concerning to me still.

 

http://puu.sh/pZBel/338c77d73b.png

http://puu.sh/pZBf3/add53bed36.png

 

Edit: 7:45 i became suspicous when ingame in wow and my latency was at a steady 55ms since my last post. So i did speed tests again and got poor result. Then i tested a different game and got poor latency results from League of legends which is the usuall during this time of day after 2pm which always is between 245-450ms. I tried to get screen shots from league but puush doesnt seem to work with it in fullscreen or windowed same with wow. I tried a different server on wow to compare on the server i usually play one and it was the saem as League of legends. I got ahead of my self and didnt make sure when i saw how it changed the night before. I aslo noticed that sometimes not often when i check my router to see any changes in logs when the down and up Fall during speed test and i find my desktop in the offline box and back in Online when i refresh.

 

http://puu.sh/pZHvm/cec2ffbd34.png

http://puu.sh/pZHxF/c66895b612.png

 

Also I would like to say sorry if all this replying and editiing im doing is realy much im trying to being as thorough as i can so incase i need to contact another twc rep or they see this from the forums mods they'll know there is somthing wrong.

Newcomer

Re: Could use Help with latency issues im having.

Sorry I cannot help with your problem, but I've been having similar issues and this seems to be the first post on the internet that matches my problem. My speed tests are consistently great while testing latency through the command prompt consistently yields 300-400ms between 6 PM and about 1 AM. So far I've:

tested and discovered the same issue on my deskop and 2 laptops (all directly connected), replaced cables, replaced the modem, and been visited by 3 technicians. 

 

I've started feeling like I'm going crazy, as the people I talk to at TWC rarely seem to understand the importance of latency. As I've told more than one suppor there: if all I needed my $80/mo. internet for was running speed tests, the service would be amazing, but since I work from home in the evenings and game online, the latency issue has shut down the entire reason I have their service. Despite my continued attempts, no one at TWC understands up to 300mbps is useless to me if I'm pinging 400ms and none of the technicians have been able to identify the issue. Details are below.

 _____

 

  • 7/6/16

On 7/6 I started experiencing some high latency in a game and noticed my connection to Discord wavering around 6-7 PM. I backed out and ran a speed test which showed everything was fine. I decided to ping Google about 20 times and was getting latency averaging 300ms. I called tech support, spent an hour on the phone, and eventually they agreed to send out a technician.

 

 

  • 7/7/16: The morning of 7/7 everything was fine per the test below.

Ping statistics for 2607:f8b0:4000:800::200e:
Packets: Sent = 94, Received = 94, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 40ms, Average = 20ms

 

The technician showed at 12 PM, ran through his tests, gave me some talk about how my cable seemed messed up, and went his way. Everything checked out: both the speed tests and my command prompt tests. 

 

That night I ran another test and got the below. 

 

Ping statistics for 2607:f8b0:4000:800::200e:
Packets: Sent = 152, Received = 152, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 463ms, Average = 327ms

 

I called tech support again who went through their tests and agreed to send a 2nd technician to checdk on the problem. 

 

 

  • 7/8/16: I recorded 3 tests at various times of the day on Friday and received the below.

Despite my showing the technician documentation from the previous night, everything checked out during his visit and he told me to keep the modem raised and, like the prior tech, switched out the cable. He was beyond useless and seemed eager to just move on since speed tests were showing him what he wanted. Absolutely zero problem solving.

 

 - 1 PM

 

Ping statistics for 2607:f8b0:4003:c17::68:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 62ms, Average = 54ms

 

 - 6 PM

 

Ping statistics for 2607:f8b0:4002:c03::68:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 123ms, Maximum = 297ms, Average = 169ms

 

 - 10 PM

 

Ping statistics for 2607:f8b0:4002:c06::6a:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 363ms, Maximum = 477ms, Average = 416ms

 

I called tech support for a 3rd time that night, spent another hour running through the same tests, and they agreed to send yet another technician. This time I requested someone visit during the later hours of the day with 6-7 PM being the latest available time.

 

 

  • 7/9/16: The 3rd technician visited and I received the times below.

 - 4 PM

 

Ping statistics for 2607:f8b0:4002:c09::93:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 107ms, Maximum = 174ms, Average = 136ms

 

The third technician considerably more helpful. He said he'd walked around the apartment before coming in to test speeds and also tested speeds at the tap. Both latency and download speed were confirmed to be spiking. He also pinged Google and ran traceroutes through the command prompt instead of relying 100% on speed tests that clearly weren't telling the whole story.

 

The tech said he put in a ticket to repair tap (or something of that nature) and I could expect a resolution this week.

 

 

  • 7/12/16: About a week later and I'm still having issues.

I called tech support again to follow up on the ticket after giving a few days for the processing to go through. Tech support said it'd been resolved Sunday and there was no issue. I was then advised to visit a store and switch out my modem. To avoid TWC having yet another "did you try this" over me, I visited the store and switched out the modem. I was unsurprised to find this did nothing.

 

I called to cancel my service and retention got invovled. I was told the ticket was never actually processed and there was no repair on the line. She asked me to allow one more technician to visit, confirm the leak or whatever it is, and get work started. I agreed, as I'd really prefer to stick with the service that was running great up until last week, and scheduled the tech for 7/15 evening.

 

_____

 

I ran some tests this evening between 7 PM and 11 PM and the results are below. 

 

 - 7 PM

 

Ping statistics for 2607:f8b0:4000:80d::2004:
Packets: Sent = 707, Received = 703, Lost = 4 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 854ms, Average = 143ms

 

 - 7:30 PM

 

Ping statistics for 2607:f8b0:4000:802::2004:
Packets: Sent = 1838, Received = 1836, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 1289ms, Average = 219ms

 

 - 11 PM

 

Ping statistics for 2607:f8b0:4000:80a::2004:
Packets: Sent = 1192, Received = 1190, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 518ms, Average = 208ms

 

 - 12:45 AM: And back down to normal like there was never a problem. 

 

Ping statistics for 216.58.194.132:
Packets: Sent = 146, Received = 146, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 122ms, Average = 26ms

 

 

I'm going to keep monitoring latency over the next couple days. Unfortunately, I'm really not sure how to read traceroutes. I'm going to try saving all I can for the next technician and pray that he's someone who'll even bother taking a look at the issue. If he is, then I apparently need to hope he actually puts in the repair ticket if he says he will. I've altogether lost any faith I might have had in TWC as the majority of their internet support seem to have no understanding of latency's impact (I'm not claiming to be an expect, but come on) and have no desire to solve a problem, instead checking off items on a list before dismissing me.

 

I hope I can provide more insight after the next technician lists or that you find a fix in the meantime.