I have the Ultimate 100 Extreme Internet package in San Antonio, TX. For several months, my ping has soared astronomically during the better part of the day, consistently slowing down between 5-12pm. After testing and tracing and recording the routes to many different servers/locations, I've come to realize that the problem likes within several nodes owned by TWC themselves. I'm a competitive gamer that has had to put a halt to streaming/practicing/playing in general due to these issues, as they permeate all of my connections.
My speeds are where they should be (higher than advertised, in fact), but the connection suffers through several TWC servers, causing my latency to skyrocket heavily. After speaking to several TWC employees online, getting my cables replaced, and talking to a Tier 3 tech, I've exhausted almost all ideas searching for a fix. Despite some of them telling me it's simply a traffic issue due to high-usage times, I can say withotu a shadow of a doubt that it was never noticeable before and I could play/watch/download anything and everything without any issues.
---
My modem levels:
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 549000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode IPv6 Only ipv6Only(1)
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 4 549000000 Hz 10.2 dBmV 44.6 dB 0 0
2 Locked QAM256 7 567000000 Hz 10.3 dBmV 44.6 dB 0 0
3 Locked QAM256 8 573000000 Hz 10.1 dBmV 44.6 dB 0 0
4 Locked QAM256 13 603000000 Hz 10.8 dBmV 44.6 dB 0 0
5 Locked QAM256 5 555000000 Hz 10.3 dBmV 44.6 dB 0 0
6 Locked QAM256 9 579000000 Hz 10.5 dBmV 44.6 dB 0 0
7 Locked QAM256 10 585000000 Hz 10.6 dBmV 44.6 dB 0 0
8 Locked QAM256 6 561000000 Hz 10.5 dBmV 44.6 dB 0 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 24200000 Hz 43.5 dBmV
2 Locked TDMA 1 2560 Ksym/sec 19400000 Hz 43.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 30600000 Hz 44.5 dBmV
4 Locked ATDMA 4 2560 Ksym/sec 37000000 Hz 43.5 dBmV
---
Trace routes (pretty par for the course during the day):
League of Legends:
Tracing route to 104.160.131.3 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1
2 20 ms 11 ms 15 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 11 ms 13 ms 23 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 22 ms 33 ms 27 ms tge0-0-9.snaxtxfp02h.texas.rr.com [24.28.132.77]
5 30 ms 11 ms 18 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 14 ms 12 ms 17 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 246 ms 245 ms 194 ms 24.175.33.4
8 226 ms 213 ms 209 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 19 ms 23 ms 20 ms 0.ae4.pr1.dfw10.tbone.rr.com [107.14.19.97]
10 170 ms 160 ms 155 ms 24.27.236.233
11 42 ms 44 ms 41 ms 104.160.134.35
12 40 ms 42 ms 45 ms ae35-br02.chi01.riotdirect.net [104.160.159.24]
13 44 ms 43 ms 42 ms 104.160.131.3
Overwatch:
Tracing route to 37.244.0.3 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1
2 22 ms 26 ms 5 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 12 ms 12 ms 17 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 183 ms 201 ms 205 ms tge0-0-8.snaxtxfp02h.texas.rr.com [24.28.134.37]
5 13 ms 13 ms 13 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 14 ms 15 ms 17 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 152 ms 142 ms 126 ms 24.175.33.4
8 272 ms 269 ms 248 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 77 ms 62 ms 79 ms bu-ether12.tustca4200w-bcr00.tbone.rr.com [66.109.6.0]
10 285 ms 235 ms 232 ms agg5.tustcaft01r.socal.rr.com [66.109.1.219]
11 56 ms 55 ms 52 ms 66.109.9.161
12 154 ms 147 ms 175 ms 37.244.0.3
Valve West:
Tracing route to eat.valve.net [192.69.96.1]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 15 ms 12 ms 10 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 14 ms 15 ms 11 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 286 ms 278 ms 280 ms tge0-0-8.snaxtxfp02h.texas.rr.com [24.28.134.37]
5 12 ms 15 ms 14 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 11 ms 17 ms 17 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 192 ms 189 ms 165 ms 24.175.33.4
8 286 ms 267 ms 259 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 29 ms 14 ms 17 ms 0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
10 24 ms 18 ms 35 ms be-202-pe03.1950stemmons.tx.ibone.comcast.net [50.248.118.169]
11 28 ms 34 ms 324 ms hu-0-4-0-2-cr02.dallas.tx.ibone.comcast.net [68.86.86.113]
12 297 ms 322 ms 359 ms be-11724-cr02.denver.co.ibone.comcast.net [68.86.84.229]
13 255 ms 263 ms 259 ms be-10817-cr01.seattle.wa.ibone.comcast.net [68.86.84.206]
14 288 ms 292 ms 265 ms hu-0-12-0-1-pe05.seattle.wa.ibone.comcast.net [68.86.84.66]
15 76 ms 65 ms 72 ms as32590-1-c.seattle.wa.ibone.comcast.net [66.208.233.26]
16 * * * Request timed out.
17 * * * Request timed out.
18 84 ms 76 ms 74 ms eat.valve.net [192.69.96.1]
Valve East:
Tracing route to iad.valve.net [208.78.164.2]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 14 ms 12 ms 27 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 17 ms 16 ms 8 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 29 ms 32 ms 21 ms tge0-0-9.snaxtxfp02h.texas.rr.com [24.28.132.77]
5 10 ms 11 ms 12 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 11 ms 12 ms 15 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 154 ms 170 ms 182 ms agg23.dllatxl301r.texas.rr.com [24.175.32.146]
8 282 ms 260 ms 242 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 278 ms 255 ms 285 ms bu-ether11.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.38]
10 54 ms 55 ms 55 ms bu-ether12.atlngamq46w-bcr00.tbone.rr.com [66.109.6.37]
11 221 ms 203 ms 213 ms bu-ether11.atlngamq47w-bcr01.tbone.rr.com [66.109.6.35]
12 46 ms 47 ms 47 ms bu-ether12.asbnva1611w-bcr00.tbone.rr.com [66.109.6.33]
13 221 ms 229 ms 198 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
14 252 ms 245 ms 268 ms 66.109.7.230
15 * * * Request timed out.
16 199 ms 44 ms 46 ms 208.78.164.2
---
As you can see, the same few addresses are proving to be problematic, namely the Roadrunner domains and a couple other reoccurring addresses.
Is there anything I can do or am I at the mercy of TWC? As it stands, I've had to essentially cease any and all competitive play and cannot take advantage of my speeds during large windows of the day for other every day tasks. There doesn't seem to be anything TWC can do for me at this point, as the many talks and checkups I've received from them have done nothing to remedy or explain the issue. The number of times they've "sent some advanced code", only to claim they've solved the issue is mind boggling. What can I do to hopefully address the problem?
↧