Didn't find what you were looking for?


We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.

A note regarding upgrades and Network Evolution:


Customers will be notified by their preferred communication method (email or text) when upgrades are available in their area
We expect 100% of our service area to be completed by end of next year

Intermittent Slow Speeds

Neil79
Neil79 Posts: 9 Novice
edited October 5 in Connectivity

Recent slow speeds with high latency for the last several days. Look at this tracert, hop 10 in particular, and you'll clearly see it's not on my end. It's been bolded and italiced. I also included another tracert, just a few minutes later, and it's performing just fine. Notice that server is no longer in the routing chain, almost like it was taken offline. My frustration is why does this keep happening, over the course of several days. If this was just a one off I wouldn't be posting. Opinions? Am I the only one seeing this?

--- Oct 1, 2026 3:26:02 PM
--- IP (wlan0) 192.168.1.3
--- IP (v4-rmnet16) 192.0.0.4
--- IP (rmnet16) 2607:fb91:17c3:d64b:ac39:c1b2:8425:9c7f
--- IP (rmnet17) 2607:fc20:8db1:9247:ad3:e80d:64da:4c84
--- Connection: WIFI

Trace to google.com

1 - 192.168.1.1
      6   11   13   (ms)
      Avg: 10 ms     Loss: 0/3 (0 %)
2 -
3 - 159.111.168.140
      lag-60.dtr02bycymi.netops.charter.com
      12   18   17   (ms)
      Avg: 15 ms     Loss: 0/3 (0 %)
4 - 96.34.32.126
      lag-19.hcr02bycymifw.netops.charter.com
      15   63   22   (ms)
      Avg: 33 ms     Loss: 0/3 (0 %)
5 - 96.34.32.64
      lag-10.hcr01bycymifw.netops.charter.com
      14   20   23   (ms)
      Avg: 19 ms     Loss: 0/3 (0 %)
6 - 96.34.32.108
      lag-428.crr01sgnwmi.netops.charter.com
      14   19   67   (ms)
      Avg: 33 ms     Loss: 0/3 (0 %)
7 - 96.34.2.56
      lag-807-10.bbr01sgnwmi.netops.charter.com
      20   27   22   (ms)
      Avg: 23 ms     Loss: 0/3 (0 %)
8 - 96.34.0.242
      lag-806.bbr01ashbva.netops.charter.com
      30   54   81   (ms)
      Avg: 55 ms     Loss: 0/3 (0 %)
9 - 96.34.3.51
      lag-801.prr01ashbva.netops.charter.com
      29   39   155   (ms)
      Avg: 74 ms     Loss: 0/3 (0 %)
10 - 68.112.12.17
      syn-068-112-012-017.biz.spectrum.com
      Loss: 3/3 (100 %)
11 - 192.178.45.33
      40   85   97   (ms)
      Avg: 74 ms     Loss: 0/3 (0 %)
12 - 192.178.242.24
      35   82   105   (ms)
      Avg: 74 ms     Loss: 0/3 (0 %)
13 - 142.251.49.189
      31   34   34   (ms)
      Avg: 33 ms     Loss: 0/3 (0 %)
14 -
15 - 192.178.124.7
      205   61   54   (ms)
      Avg: 106 ms     Loss: 0/3 (0 %)
16 - 142.251.234.37
      131   153   60   (ms)
      Avg: 114 ms     Loss: 0/3 (0 %)
17 - 192.178.249.235
      55   146   166   (ms)
      Avg: 122 ms     Loss: 0/3 (0 %)
18 - 142.251.231.67
      47   98   53   (ms)
      Avg: 66 ms     Loss: 0/3 (0 %)
19 - 142.251.34.238
      ncorda-an-in-f14.1e100.net
      59   140   59   (ms)
      Avg: 86 ms     Loss: 0/3 (0 %)

Below is a good tracert, and how it should be.

--- Oct 1, 2026 3:42:57 PM
--- IP (wlan0) 192.168.1.3
--- IP (v4-rmnet16) 192.0.0.4
--- IP (rmnet16) 2607:fb91:17c3:d64b:ac39:c1b2:8425:9c7f
--- IP (rmnet17) 2607:fc20:8db1:9247:ad3:e80d:64da:4c84
--- Connection: WIFI

Trace to google.com

1 - 192.168.1.1
      6   19   71   (ms)
      Avg: 32 ms     Loss: 0/3 (0 %)
2 -
3 - 159.111.168.140
      lag-60.dtr02bycymi.netops.charter.com
      15   27   25   (ms)
      Avg: 22 ms     Loss: 0/3 (0 %)
4 - 96.34.32.126
      lag-19.hcr02bycymifw.netops.charter.com
      16   47   66   (ms)
      Avg: 43 ms     Loss: 0/3 (0 %)
5 - 96.34.32.64
      lag-10.hcr01bycymifw.netops.charter.com
      17   29   22   (ms)
      Avg: 22 ms     Loss: 0/3 (0 %)
6 - 96.34.32.108
      lag-428.crr01sgnwmi.netops.charter.com
      14   61   18   (ms)
      Avg: 31 ms     Loss: 0/3 (0 %)
7 - 96.34.2.56
      lag-807-10.bbr01sgnwmi.netops.charter.com
      17   18   20   (ms)
      Avg: 18 ms     Loss: 0/3 (0 %)
8 - 96.34.0.242
      lag-806.bbr01ashbva.netops.charter.com
      30   35   79   (ms)
      Avg: 48 ms     Loss: 0/3 (0 %)
9 - 96.34.3.51
      lag-801.prr01ashbva.netops.charter.com
      31   35   37   (ms)
      Avg: 34 ms     Loss: 0/3 (0 %)
10 - 72.14.219.176
      32   33   32   (ms)
      Avg: 32 ms     Loss: 0/3 (0 %)
11 - 192.178.248.17
      33   37   35   (ms)
      Avg: 35 ms     Loss: 0/3 (0 %)
12 - 192.178.248.40
      36   54   39   (ms)
      Avg: 43 ms     Loss: 0/3 (0 %)
13 - 216.239.50.93
      39   35   34   (ms)
      Avg: 36 ms     Loss: 0/3 (0 %)
14 - 142.250.215.191
      35   103   89   (ms)
      Avg: 75 ms     Loss: 0/3 (0 %)
15 - 192.178.124.3
      46   61   97   (ms)
      Avg: 68 ms     Loss: 0/3 (0 %)
16 - 209.85.241.122
      84   70   69   (ms)
      Avg: 74 ms     Loss: 0/3 (0 %)
17 - 142.251.254.45
      48   63   95   (ms)
      Avg: 68 ms     Loss: 0/3 (0 %)
18 - 142.251.231.245
      52   299   103   (ms)
      Avg: 151 ms     Loss: 0/3 (0 %)
19 - 142.251.211.14
      pnorda-am-in-f14.1e100.net
      48   105   65   (ms)
      Avg: 72 ms     Loss: 0/3 (0 %)

Comments

  • Tyleen_Z
    Tyleen_Z Posts: 1,146 ✅ Verified Employee Moderator

    Hello and welcome to the Spectrum Community!

    I do apologize for the issues you're having with out internet service. From what I can see with the first trace route is that at hop 10 is when the signal transitions from our network to outside of the network. This is a normal result since the issues do not continue after hop 10 and do not show before that it means that specific edge router is designed to ignore trace routes so then would show a 100% packet loss. The second trace route shows a different location for hop 10 because hops are not always going to be the same. If you were to see issues before hop 10 consistently then the issue would be on our end.

    I was able to find your account using your community login and the signal to your modem looks fine.

    When you notice the service issues do you see the issues on all devices? Do you notice the issues only when doing certain things like streaming or gaming?

    -Tyleen

  • Neil79
    Neil79 Posts: 9 Novice

    Thank you for getting back with me so quickly. I also called support, and I asked if I could send in my tracerts for Level 3. The support representative unfortunately stated that he felt the issue was with my end, and wanted to schedule a technician. He didn't know what a tracert was, and insisted that Spectrum doesn't have or lease any server bandwidth. I told them I would hold off on the service call, since the tracerts all show the slow downs happening well downstream from me most likely at one of Charter's Edge data centers. In answer to your question, the slow downs effect all of my connected equipment. It only happens during certain times of the day, but usually toward the afternoon. One thing that seems to be in common is that it occurs around hop 10, and that first server ip address is a major contributing player. I just ran another tracert showing that very same unresponsive server. I am also attaching a ping test as well to show the inconsistent latency along that route as well. Thank you for your time, and fast response.

    --- Oct 1, 2026 6:09:54 PM
    --- IP (wlan0) 192.168.1.3
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17c3:d64b:ac39:c1b2:8425:9c7f
    --- IP (rmnet17) 2607:fc20:8db1:9247:ad3:e80d:64da:4c84
    --- Connection: WIFI

    Trace to google.com

    1 - 192.168.1.1
          5   63   64   (ms)
          Avg: 44 ms     Loss: 0/3 (0 %)
    2 -
    3 - 159.111.168.140
          lag-60.dtr02bycymi.netops.charter.com
          14   64   34   (ms)
          Avg: 37 ms     Loss: 0/3 (0 %)
    4 - 96.34.32.126
          lag-19.hcr02bycymifw.netops.charter.com
          15   28   20   (ms)
          Avg: 21 ms     Loss: 0/3 (0 %)
    5 - 96.34.32.64
          lag-10.hcr01bycymifw.netops.charter.com
          19   20   67   (ms)
          Avg: 35 ms     Loss: 0/3 (0 %)
    6 - 96.34.32.108
          lag-428.crr01sgnwmi.netops.charter.com
          15   64   57   (ms)
          Avg: 45 ms     Loss: 0/3 (0 %)
    7 - 96.34.2.56
          lag-807-10.bbr01sgnwmi.netops.charter.com
          13   25   72   (ms)
          Avg: 36 ms     Loss: 0/3 (0 %)
    8 - 96.34.0.242
          lag-806.bbr01ashbva.netops.charter.com
          33   39   41   (ms)
          Avg: 37 ms     Loss: 0/3 (0 %)
    9 - 96.34.3.51
          lag-801.prr01ashbva.netops.charter.com
          42   43   41   (ms)
          Avg: 42 ms     Loss: 0/3 (0 %)
    10 - 68.112.12.17
          syn-068-112-012-017.biz.spectrum.com
          Loss: 3/3 (100 %)
    11 - 192.178.45.33
          30   36   34   (ms)
          Avg: 33 ms     Loss: 0/3 (0 %)
    12 - 192.178.242.26
          37   42   37   (ms)
          Avg: 38 ms     Loss: 0/3 (0 %)
    13 -
    14 - 142.251.237.185
          39   39   38   (ms)
          Avg: 38 ms     Loss: 0/3 (0 %)
    15 - 192.178.124.3
          51   53   51   (ms)
          Avg: 51 ms     Loss: 0/3 (0 %)
    16 - 216.239.57.76
          55   157   61   (ms)
          Avg: 91 ms     Loss: 0/3 (0 %)
    17 - 192.178.105.217
          54   145   166   (ms)
          Avg: 121 ms     Loss: 0/3 (0 %)
    18 - 142.251.61.41
          55   58   95   (ms)
          Avg: 69 ms     Loss: 0/3 (0 %)
    19 - 142.250.177.238
          pnorda-an-in-f14.1e100.net
          76   94   116   (ms)
          Avg: 95 ms     Loss: 0/3 (0 %)

    --- Oct 1, 2026 6:11:33 PM
    --- IP (wlan0) 192.168.1.3
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17c3:d64b:ac39:c1b2:8425:9c7f
    --- IP (rmnet17) 2607:fc20:8db1:9247:ad3:e80d:64da:4c84
    --- Connection: WIFI

    Pinging port 80 on google.com

    1 time=87 ms, avg=87 ms
    2 time=74 ms, avg=80 ms
    3 time=119 ms, avg=93 ms
    4 time=122 ms, avg=100 ms
    5 time=58 ms, avg=92 ms
    6 time=97 ms, avg=92 ms
    7 time=69 ms, avg=89 ms
    8 time=76 ms, avg=87 ms
    9 time=124 ms, avg=91 ms
    10 time=68 ms, avg=89 ms
    11 time=120 ms, avg=92 ms
    12 time=68 ms, avg=92 ms
    13 time=75 ms, avg=87 ms
    14 time=189 ms, avg=94 ms
    15 time=72 ms, avg=95 ms
    16 time=71 ms, avg=93 ms
    17 time=129 ms, avg=99 ms
    18 time=101 ms, avg=101 ms
    19 time=71 ms, avg=96 ms
    20 time=102 ms, avg=99 ms

    min=58 ms
    avg=94 ms
    max=189 ms
    0/20 dropped:   0 %

  • RAIST515O
    RAIST515O Posts: 348 Contributor
    edited October 2

    Just like cars on a highway or going through downtown, packets can simply get stuck in a queue. They typically are not actually getting discarded, but delayed here and there. It is why there are things like congestion control and lag compensation.

    There is going to be jitter on the internet, especially as systems become more reliant on buffering to provide over the top high speed bursting.

    If you truly need to keep jitter tightened as much as possible, may want to look into something like optimizing QoS through your router or other device.

    https://www.waveform.com/tools/bufferbloat

    https://www.waveform.com/tools/bufferbloat

  • Neil79
    Neil79 Posts: 9 Novice
    edited October 2

    Looking better this morning. Hopefully it looks similar this afternoon. 👍 Thank you Tyleen for your help. You taught me something about the Edge data centers, and how not all of the servers respond to ICMP echo requests. Below are this mornings figures.

    --- Oct 2, 2026 10:32:40 AM
    --- IP (wlan0) 192.168.1.3
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17ed:6374:ac39:c1b8:9cd7:edd3
    --- IP (rmnet17) 2607:fc20:8da8:af1f:ad3:e80d:7d57:c142
    --- Connection: WIFI

    Trace to google.com

    1 - 192.168.1.1
          8   11   14   (ms)
          Avg: 11 ms     Loss: 0/3 (0 %)
    2 -
    3 - 159.111.168.140
          lag-59.hcr12bycymifw.netops.charter.com
          15   36   20   (ms)
          Avg: 23 ms     Loss: 0/3 (0 %)
    4 - 192.62.248.248
          lag-20.hcr02bycymifw.netops.charter.com
          17   74   31   (ms)
          Avg: 40 ms     Loss: 0/3 (0 %)
    5 - 192.62.248.240
          lag-47.rcr01antsmiad.netops.charter.com
          25   39   29   (ms)
          Avg: 31 ms     Loss: 0/3 (0 %)
    6 - 96.34.32.228
          lag-6.crr01aldlmi.netops.charter.com
          25   51   37   (ms)
          Avg: 37 ms     Loss: 0/3 (0 %)
    7 - 96.34.2.8
          lag-807-10.bbr01aldlmi.netops.charter.com
          Loss: 3/3 (100 %)
    8 - 96.34.0.139
          lag-805.bbr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    9 - 96.34.3.119
          lag-811.prr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    10 - 96.34.152.155
          syn-096-034-152-155.inf.spectrum.com
          Loss: 3/3 (100 %)
    11 - 192.178.249.201
          27   41   38   (ms)
          Avg: 35 ms     Loss: 0/3 (0 %)
    12 - 142.251.231.247
          30   41   38   (ms)
          Avg: 36 ms     Loss: 0/3 (0 %)
    13 - 142.251.211.14
          pnorda-am-in-f14.1e100.net
          33   35   43   (ms)
          Avg: 37 ms     Loss: 0/3 (0 %)

    --- Oct 2, 2026 10:36:58 AM
    --- IP (wlan0) 192.168.1.3
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17ed:6374:ac39:c1b8:9cd7:edd3
    --- IP (rmnet17) 2607:fc20:8da8:af1f:ad3:e80d:7d57:c142
    --- Connection: WIFI

    Pinging port 80 on google.com

    1 time=36 ms, avg=36 ms
    2 time=83 ms, avg=59 ms
    3 time=88 ms, avg=69 ms
    4 time=44 ms, avg=62 ms
    5 time=94 ms, avg=69 ms
    6 time=40 ms, avg=64 ms
    7 time=47 ms, avg=61 ms
    8 time=84 ms, avg=64 ms
    9 time=44 ms, avg=62 ms
    10 time=43 ms, avg=60 ms
    11 time=44 ms, avg=61 ms
    12 time=36 ms, avg=56 ms
    13 time=53 ms, avg=52 ms
    14 time=40 ms, avg=52 ms
    15 time=49 ms, avg=48 ms
    16 time=34 ms, avg=47 ms
    17 time=49 ms, avg=47 ms
    18 time=44 ms, avg=43 ms
    19 time=47 ms, avg=43 ms
    20 time=83 ms, avg=47 ms

    min=34 ms
    avg=54 ms
    max=94 ms
    0/20 dropped:   0 %

  • Neil79
    Neil79 Posts: 9 Novice

    Back to terrible performance after decent weekend service. This is happening right at my local headend. I can't even stream music without frequent freezing, and rebuffering. 🤦‍♂️

    Here is a tracert taken minutes ago, and it shows severe packet loss on Spectrum's end. Can you please advise on what these ongoing service disruptions are related to? How long will they continue to last? We have been loyal customers for over twenty-years. I would hate to have to jump to fiber over this ongoing issue. 😔 Thank you again!

    --- Oct 5, 2026 10:18:48 AM
    --- IP (wlan0) 192.168.1.29
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17c3:20f7:ad3:e852:8401:28f2
    --- IP (rmnet17) 2607:fc20:8dc3:baeb:ad3:e80d:4b5a:4151
    --- Connection: WIFI

    Trace to tidal.com

    1 - 192.168.1.1
          8   10   56   (ms)
          Avg: 24 ms     Loss: 0/3 (0 %)
    2 -
    3 - 159.111.168.140
          lag-59.hcr12bycymifw.netops.charter.com
          78   48   (ms)
          Avg: 63 ms     Loss: 1/3 (50 %)
    4 - 192.62.248.248
          lag-20.hcr02bycymifw.netops.charter.com
          19   48   188   (ms)
          Avg: 85 ms     Loss: 0/3 (0 %)
    5 - 192.62.248.240
          lag-47.rcr01antsmiad.netops.charter.com
          46   143   (ms)
          Avg: 94 ms     Loss: 1/3 (50 %)
    6 - 96.34.32.228
          lag-6.crr01aldlmi.netops.charter.com
          167   186   31   (ms)
          Avg: 128 ms     Loss: 0/3 (0 %)
    7 - 96.34.2.8
          lag-807-10.bbr01aldlmi.netops.charter.com
          Loss: 3/3 (100 %)
    8 - 96.34.0.193
          lag-905.bbr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    9 - 96.34.3.9
          lag-801.prr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    10 -
    11 -
    12 -
    13 -
    14 - 15.230.192.12
          Loss: 3/3 (100 %)
    15 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          37   156   (ms)
          Avg: 96 ms     Loss: 1/3 (50 %)
    16 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          187   34   (ms)
          Avg: 110 ms     Loss: 1/3 (50 %)
    17 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          49   196   55   (ms)
          Avg: 100 ms     Loss: 0/3 (0 %)
    18 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          171   (ms)
          Avg: 171 ms     Loss: 2/3 (200 %)
    19 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          35   (ms)
          Avg: 35 ms     Loss: 2/3 (200 %)
    20 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          166   37   (ms)
          Avg: 101 ms     Loss: 1/3 (50 %)
    21 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          38   30   (ms)
          Avg: 34 ms     Loss: 1/3 (50 %)
    22 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          32   178   (ms)
          Avg: 105 ms     Loss: 1/3 (50 %)
    23 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          52   124   (ms)
          Avg: 88 ms     Loss: 1/3 (50 %)
    24 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          31   175   (ms)
          Avg: 103 ms     Loss: 1/3 (50 %)
    25 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          115   238   31   (ms)
          Avg: 128 ms     Loss: 0/3 (0 %)
    26 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          29   32   34   (ms)
          Avg: 31 ms     Loss: 0/3 (0 %)
    27 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          29   144   284   (ms)
          Avg: 152 ms     Loss: 0/3 (0 %)
    28 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          29   42   (ms)
          Avg: 35 ms     Loss: 1/3 (50 %)
    29 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          77   201   33   (ms)
          Avg: 103 ms     Loss: 0/3 (0 %)

          31   (ms)
          Avg: 31 ms     Loss: 2/3 (200 %)

  • Neil79
    Neil79 Posts: 9 Novice

    Thirty minutes and we're back to good, and looking great. Same exact servers too, you can check the ip addresses in bold again. This is frustrating. I just wish there was some communication about what's going on. 🤷‍♂️

    --- Oct 5, 2026 10:55:08 AM
    --- IP (wlan0) 192.168.1.29
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17c5:437e:ac39:c1b2:6aef:2950
    --- IP (rmnet17) 2607:fc20:8dc3:baeb:ad3:e80d:4b5a:4151
    --- Connection: WIFI

    Trace to tidal.com

    1 - 192.168.1.1
          5   16   12   (ms)
          Avg: 11 ms     Loss: 0/3 (0 %)
    2 -
    3 - 159.111.168.140
          lag-59.hcr12bycymifw.netops.charter.com
          15   77   19   (ms)
          Avg: 37 ms     Loss: 0/3 (0 %)
    4 - 192.62.248.248
          lag-20.hcr02bycymifw.netops.charter.com
          24   16   18   (ms)
          Avg: 19 ms     Loss: 0/3 (0 %)
    5 - 192.62.248.240
          lag-47.rcr01antsmiad.netops.charter.com
          24   30   39   (ms)
          Avg: 31 ms     Loss: 0/3 (0 %)
    6 - 96.34.32.228
          lag-6.crr01aldlmi.netops.charter.com
          28   25   55   (ms)
          Avg: 36 ms     Loss: 0/3 (0 %)
    7 - 96.34.2.8
          lag-807-10.bbr01aldlmi.netops.charter.com
          Loss: 3/3 (100 %)
    8 - 96.34.0.193
          lag-905.bbr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    9 - 96.34.3.9
          lag-801.prr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    10 -
    11 -
    12 -
    13 -
    14 - 15.230.192.12
          Loss: 3/3 (100 %)
    15 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          26   34   29   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    16 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          28   28   26   (ms)
          Avg: 27 ms     Loss: 0/3 (0 %)
    17 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          26   29   28   (ms)
          Avg: 27 ms     Loss: 0/3 (0 %)
    18 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          26   33   26   (ms)
          Avg: 28 ms     Loss: 0/3 (0 %)
    19 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          27   30   28   (ms)
          Avg: 28 ms     Loss: 0/3 (0 %)
    20 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          29   29   28   (ms)
          Avg: 28 ms     Loss: 0/3 (0 %)
    21 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          31   33   29   (ms)
          Avg: 31 ms     Loss: 0/3 (0 %)
    22 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          27   33   28   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    23 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          28   31   42   (ms)
          Avg: 33 ms     Loss: 0/3 (0 %)
    24 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          25   30   27   (ms)
          Avg: 27 ms     Loss: 0/3 (0 %)
    25 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          28   30   29   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    26 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          26   30   31   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    27 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          36   33   30   (ms)
          Avg: 33 ms     Loss: 0/3 (0 %)
    28 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          27   27   27   (ms)
          Avg: 27 ms     Loss: 0/3 (0 %)
    29 - 108.159.227.15
          server-108-159-227-15.ord56.r.cloudfront.net
          30   28   27   (ms)
          Avg: 28 ms     Loss: 0/3 (0 %)

          28   32   33   (ms)
          Avg: 31 ms     Loss: 0/3 (0 %)

  • James_M
    James_M Posts: 5,656 ✅ Verified Employee Moderator

    Have you tried replicating the issue while bypassing the router and connecting directly to the modem?

  • Neil79
    Neil79 Posts: 9 Novice

    Hi everyone. My last post on this, because I know I'm sounding like a broken record. Here we go back to bad again. James, in answer to your question, no I haven't because the tracert takes care of all that troubleshooting. It very clearly shows that my router connection is very stable, with no loss and sub ten millisecond latency, and that all of the degradation is occurring off-site (hop 4 is well downstream from my local network) at the ip addresses indicated in bold. You can whois them, and they all point to Charter managed. Although, I had the names resolved when I ran the tracert, so you don't even have to run the whois since it's right there as clear as day at the Bay City Charter server. Thank you for trying though. I will try and stick this out with Charter, but it's just very frustrating. 😔 Here's my tracert to Tidal again, as streaming music has become impossible with Charter dropping packets.. 🤦‍♂️

    --- Oct 5, 2026 12:26:28 PM
    --- IP (wlan0) 192.168.1.29
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17c5:437e:ac39:c1b2:6aef:2950
    --- IP (rmnet17) 2607:fc20:8dc3:baeb:ad3:e80d:4b5a:4151
    --- Connection: WIFI

    Trace to tidal.com

    1 - 192.168.1.1
          5   9   7   (ms)
          Avg: 7 ms     Loss: 0/3 (0 %)
    2 -
    3 - 159.111.168.140
          lag-59.hcr12bycymifw.netops.charter.com
          12   21   176   (ms)
          Avg: 69 ms     Loss: 0/3 (0 %)
    4 - 192.62.248.248
          lag-20.hcr02bycymifw.netops.charter.com
          18   164   (ms)
          Avg: 91 ms     Loss: 1/3 (50 %)
    5 - 192.62.248.240
          lag-47.rcr01antsmiad.netops.charter.com
          31   28   25   (ms)
          Avg: 28 ms     Loss: 0/3 (0 %)
    6 - 96.34.32.228
          lag-6.crr01aldlmi.netops.charter.com
          29   25   170   (ms)
          Avg: 74 ms     Loss: 0/3 (0 %)
    7 - 96.34.2.8
          lag-807-10.bbr01aldlmi.netops.charter.com
          Loss: 3/3 (100 %)
    8 - 96.34.0.193
          lag-905.bbr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    9 - 96.34.3.9
          lag-801.prr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    10 -
    11 -
    12 -
    13 -
    14 - 15.230.192.12
          Loss: 3/3 (100 %)
    15 - 108.159.227.57
          server-108-159-227-57.ord56.r.cloudfront.net
          35   34   167   (ms)
          Avg: 78 ms     Loss: 0/3 (0 %)

  • James_M
    James_M Posts: 5,656 ✅ Verified Employee Moderator
    edited October 5

    Trace routes often de-prioritize hops, showing packet loss that is not packet loss, just a lack of a response. There also appears to be some congestion, which is normal. If there was truly a network issue affecting delivery, it would be present on all subsequent hops. The final hop 15 shows no packet loss:


    15 - 108.159.227.57
          server-108-159-227-57.ord56.r.cloudfront.net
          35   34   167   (ms)
          Avg: 78 ms     Loss: 0/3 (0 %)

    Which means it was completed without an issue. If there is an issue with your router, it is possible that it is magnifying the normal congestion. Bypassing the router and connecting directly to the modem isolates any possible equipment issue with your router and is the next step in troubleshooting. Let us know how it goes.

  • Neil79
    Neil79 Posts: 9 Novice

    James, if I didn't have any symptoms associated with a congested or degraded isp connection I would be inclined to agree with your last statement. Also, faulty equipment doesn't exhibit the symptoms I am having. This tracert, the first one which was from this morning, and shows loss prompegating to the final hope is not normal congestion by any means. I have been monitoring this intermittent situation for a week, and it is network related not my router. As I write this Spectrum is performing flawlessly. Unfortunately, due to character constraints I will have to paste it into the next comment. If you compare that two, you will easily see this is a Spectrum issue. Thank you for your time and hard work. In my many years of sales and technical support, some of those even spent at Charter, service isn't always recognized. I do appreciate you looking into not just my problem but everyone else you assist. 👍

    --- Oct 5, 2026 10:18:48 AM
    --- IP (wlan0) 192.168.1.29
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17c3:20f7:ad3:e852:8401:28f2
    --- IP (rmnet17) 2607:fc20:8dc3:baeb:ad3:e80d:4b5a:4151
    --- Connection: WIFI

    Trace to tidal.com

    1 - 192.168.1.1
    8 10 56 (ms)
    Avg: 24 ms Loss: 0/3 (0 %)
    2 -
    3 - 159.111.168.140
    lag-59.hcr12bycymifw.netops.charter.com
    78 48 (ms)
    Avg: 63 ms Loss: 1/3 (50 %)
    4 - 192.62.248.248
    lag-20.hcr02bycymifw.netops.charter.com
    19 48 188 (ms)
    Avg: 85 ms Loss: 0/3 (0 %)
    5 - 192.62.248.240
    lag-47.rcr01antsmiad.netops.charter.com
    46 143 (ms)
    Avg: 94 ms Loss: 1/3 (50 %)
    6 - 96.34.32.228
    lag-6.crr01aldlmi.netops.charter.com
    167 186 31 (ms)
    Avg: 128 ms Loss: 0/3 (0 %)
    7 - 96.34.2.8
    lag-807-10.bbr01aldlmi.netops.charter.com
    Loss: 3/3 (100 %)
    8 - 96.34.0.193
    lag-905.bbr01chcgil.netops.charter.com
    Loss: 3/3 (100 %)
    9 - 96.34.3.9
    lag-801.prr01chcgil.netops.charter.com
    Loss: 3/3 (100 %)
    10 -
    11 -
    12 -
    13 -
    14 - 15.230.192.12
    Loss: 3/3 (100 %)
    15 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    37 156 (ms)
    Avg: 96 ms Loss: 1/3 (50 %)
    16 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    187 34 (ms)
    Avg: 110 ms Loss: 1/3 (50 %)
    17 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    49 196 55 (ms)
    Avg: 100 ms Loss: 0/3 (0 %)
    18 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    171 (ms)
    Avg: 171 ms Loss: 2/3 (200 %)
    19 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    35 (ms)
    Avg: 35 ms Loss: 2/3 (200 %)
    20 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    166 37 (ms)
    Avg: 101 ms Loss: 1/3 (50 %)
    21 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    38 30 (ms)
    Avg: 34 ms Loss: 1/3 (50 %)
    22 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    32 178 (ms)
    Avg: 105 ms Loss: 1/3 (50 %)
    23 - 108.159.227.15
    server-108-159-227-15.ord56.r.cloudfront.net
    52 124 (ms)
    Avg: 88 ms Loss: 1/3 (50 %)
    24 - 108.159.227.118
    server-108-159-227-118.ord56.r.cloudfront.net
    31 175 (ms)
    Avg: 103 ms Loss: 1/3 (50 %)
    25 - 108.159.227.118
    server-108-159-227-118.ord56.r.cloudfront.net
    115 238 31 (ms)
    Avg: 128 ms Loss: 0/3 (0 %)
    26 - 108.159.227.118
    server-108-159-227-118.ord56.r.cloudfront.net
    29 32 34 (ms)
    Avg: 31 ms Loss: 0/3 (0 %)
    27 - 108.159.227.118
    server-108-159-227-118.ord56.r.cloudfront.net
    29 144 284 (ms)
    Avg: 152 ms Loss: 0/3 (0 %)
    28 - 108.159.227.118
    server-108-159-227-118.ord56.r.cloudfront.net
    29 42 (ms)
    Avg: 35 ms Loss: 1/3 (50 %)
    29 - 108.159.227.118
    server-108-159-227-118.ord56.r.cloudfront.net
    77 201 33 (ms)
    Avg: 103 ms Loss: 0/3 (0 %)

      31   (ms)
  Avg: 31 ms     Loss: 2/3 (200 %)
  • Neil79
    Neil79 Posts: 9 Novice

    For comparison.. One beauty of a tracert! 👌

    --- Oct 5, 2026 2:30:44 PM
    --- IP (wlan0) 192.168.1.29
    --- IP (v4-rmnet16) 192.0.0.4
    --- IP (rmnet16) 2607:fb91:17c5:437e:ac39:c1b2:6aef:2950
    --- IP (rmnet17) 2607:fc20:8dc3:baeb:ad3:e80d:4b5a:4151
    --- Connection: WIFI

    Trace to tidal.com

    1 - 192.168.1.1
          6   15   10   (ms)
          Avg: 10 ms     Loss: 0/3 (0 %)
    2 -
    3 - 159.111.168.140
          lag-59.hcr12bycymifw.netops.charter.com
          13   17   30   (ms)
          Avg: 20 ms     Loss: 0/3 (0 %)
    4 - 192.62.248.248
          lag-20.hcr02bycymifw.netops.charter.com
          28   31   34   (ms)
          Avg: 31 ms     Loss: 0/3 (0 %)
    5 - 192.62.248.240
          lag-47.rcr01antsmiad.netops.charter.com
          22   28   37   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    6 - 96.34.32.228
          lag-6.crr01aldlmi.netops.charter.com
          25   38   39   (ms)
          Avg: 34 ms     Loss: 0/3 (0 %)
    7 - 96.34.2.8
          lag-807-10.bbr01aldlmi.netops.charter.com
          Loss: 3/3 (100 %)
    8 - 96.34.0.193
          lag-905.bbr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    9 - 96.34.3.119
          lag-811.prr01chcgil.netops.charter.com
          Loss: 3/3 (100 %)
    10 -
    11 -
    12 -
    13 -
    14 - 15.230.192.12
          Loss: 3/3 (100 %)
    15 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          27   32   30   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    16 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          33   31   27   (ms)
          Avg: 30 ms     Loss: 0/3 (0 %)
    17 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          27   30   30   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    18 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          30   29   26   (ms)
          Avg: 28 ms     Loss: 0/3 (0 %)
    19 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          30   30   28   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    20 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          28   29   30   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    21 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          28   27   29   (ms)
          Avg: 28 ms     Loss: 0/3 (0 %)
    22 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          27   27   29   (ms)
          Avg: 27 ms     Loss: 0/3 (0 %)
    23 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          27   29   31   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    24 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          26   28   33   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    25 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          28   30   30   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    26 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          31   30   26   (ms)
          Avg: 29 ms     Loss: 0/3 (0 %)
    27 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          29   28   25   (ms)
          Avg: 27 ms     Loss: 0/3 (0 %)
    28 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          27   27   27   (ms)
          Avg: 27 ms     Loss: 0/3 (0 %)
    29 - 108.159.227.118
          server-108-159-227-118.ord56.r.cloudfront.net
          27   29   28   (ms)
          Avg: 28 ms     Loss: 0/3 (0 %)

          31   32   77   (ms)
          Avg: 46 ms     Loss: 0/3 (0 %)

  • RAIST515O
    RAIST515O Posts: 348 Contributor
    edited October 5

    Packets are not getting discarded, but held in queues is what @James_M was describing. Not every application recovers gracefully from delayed/out of order packet delivery. One of the bigger risks (and drawbacks) of things like UDP to try to get less overhead and swifter transfers compared to TCP.

    A large contributer to this is buffer bloating, which is often exacerbated by routers. Networks are becoming more and more dependent on burst transmissions, and extra layers of buffers can cause things to get sliced up in weird ways. If your jitter is becoming a problem, may want to look into something like QoS to try smoothing the timeslicing out better... not everything on your network needs to be thrust through at maximum speed, and if your network is doing that, packets that DO need higher priority may get queued behind slower traffic... because so much of your traffic is by default put on the wire as vanilla best effort, in FIFO order.

  • Neil79
    Neil79 Posts: 9 Novice

    RAIST515O, thank you for your suggestion. However, my LAN jitter is great and typically my Spectrum WAN jitter is likewise very good. I manage my homes gigabit connection with approximately fourty clients. Since around 18:30 GMT things have been wonderful, again supported by much improved latency and tracert logs (see below). Hopefully they don't start messing with servers again tomorrow. Everytime I've had major internet slow downs it has been clearly indicated when I run a tracert. The problems were real, and they weren't client side they were clearly server side. Hopefully Charter keeps it sorted out. 🤞

    --- Oct 5, 2026 8:39:52 PM

    --- IP (wlan0) 192.168.1.29

    --- IP (v4-rmnet16) 192.0.0.4

    --- IP (rmnet16) 2607:fb91:17c5:437e:ac39:c1b2:6aef:2950

    --- IP (rmnet17) 2607:fc20:8dc3:baeb:ad3:e80d:4b5a:4151

    --- Connection: WIFI

    Pinging port 80 on tidal.com

    1 time=33 ms, avg=33 ms

    2 time=39 ms, avg=36 ms

    3 time=52 ms, avg=41 ms

    4 time=92 ms, avg=54 ms

    5 time=47 ms, avg=52 ms

    6 time=39 ms, avg=50 ms

    7 time=94 ms, avg=56 ms

    8 time=37 ms, avg=54 ms

    9 time=49 ms, avg=53 ms

    10 time=37 ms, avg=51 ms

    11 time=46 ms, avg=53 ms

    12 time=51 ms, avg=54 ms

    13 time=47 ms, avg=53 ms

    14 time=36 ms, avg=48 ms

    15 time=46 ms, avg=48 ms

    16 time=40 ms, avg=48 ms

    17 time=50 ms, avg=43 ms

    18 time=41 ms, avg=44 ms

    19 time=51 ms, avg=44 ms

    20 time=42 ms, avg=45 ms

    min=33 ms

    avg=48 ms

    max=94 ms

    0/20 dropped: 0 %

Categories