how-to block ads
|
CALS
@rr.com
| reply to dbmaven
Re: [TWC] NYC - Slow Speeds, Part 2
Ive had called into TWC nearly every day for the past week. On Friday someone from Tier 3 called me back to let me know the problem was escalated, and should be rectified. I told them the problem starts around 8pm, so I check it out and see.
That Friday latency was improved (down to 500ms from 700ms), but still horrible. On Saturday latency was tolerable (200ms). Sunday latency was back to 600ms.
One would think that this 10Gig Router is congested/saturated in the evenings, and on the weekends (Fri/Sat) the problem isnt as severe because fewer people are online.
TWC's evaluation and escalation process is geared towards those with absolutely no knowledge about computer or networking. For anyone who has worked with a computer or has any network knowledge, its not rocket science to determine where about the problem is. There techs (even Tier 3) are like tits on a bull. They spend more time asking if I am behind a linksys router, then looking at the information, logs, traces we provide to them.
It takes two managers/supervisors to have an issue escalated at all from Tier 3. Its like they have system in place which prevents anything from getting past Tier 3.
These Tier 3 guys (most of the ones that I have dealt with), are just more technical canned script readers (Are you behind a modem, did you reset your modem, what OS are you running ...).
Every day I call TWC for my credit and every day I file a complaint with DoITT. | |
former tech
@rr.com
|  guys and gals.
there is a problem, still.
on friday and saturday nights the internet is not as saturated, more people are not on it. i had good gaming on friday and saturday. sunday was lagged again. this has been going on for 2+ weeks. unplayable.
I suggest we use our tracerts rather than speedtests, or both.
the problem has just started for me tonight. i changed my modem to entertain level 3. here are my tracerts with time documentations.
C:\Users\daddy>tracert www.yahoo.com
Tracing route to www.yahoo-ht3.akadns.net [69.147.76.15]
over a maximum of 30 hops:
1 8 ms 9 ms 9 ms x.x.x.x
2 10 ms 10 ms 9 ms gig-5-1-nycmnys-rtr1.nyc.rr.com [24.29.100.45]
3 8 ms 9 ms 9 ms pos-1-0-nycmnyl-rtr2.nyc.rr.com [24.29.100.13]
4 10 ms 10 ms 9 ms tenge12-1-0-nycmnya-rtr1.nyc.rr.com [24.29.97.42
]
5 9 ms 9 ms 10 ms tenge-2-0-0-nwrknjmd-rtr.nyc.rr.com [24.29.119.1
10]
6 23 ms 11 ms 9 ms ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
7 17 ms 15 ms 15 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
8 17 ms 19 ms 19 ms ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.167]
9 16 ms 15 ms 15 ms 66.109.9.167
10 14 ms 16 ms 27 ms ae2-p171.msr2.re1.yahoo.com [216.115.108.71]
11 18 ms 18 ms 17 ms ge-1-44.bas-a2.re3.yahoo.com [66.196.112.207]
12 15 ms 16 ms 14 ms f1.www.vip.re1.yahoo.com [69.147.76.15]
Trace complete.
C:\Users\daddy> 5:32PM
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\daddy>tracert www.yahoo.com
Tracing route to www.yahoo-ht3.akadns.net [69.147.76.15]
over a maximum of 30 hops:
1 19 ms 14 ms 8 ms x.x.x.x
2 8 ms 7 ms 7 ms gig-0-3-nycmnys-ubr6.nyc.rr.com [24.29.100.50]
3 8 ms 8 ms 7 ms gig-4-1-nycmnys-rtr2.nyc.rr.com [24.29.100.53]
4 8 ms 7 ms 19 ms pos-1-1-nycmnya-rtr2.nyc.rr.com [24.29.130.58]
5 18 ms 17 ms 9 ms tenge-3-0-0-nycsnyoo-rtr1.nyc.rr.com [24.29.119.
114]
6 19 ms 10 ms 9 ms 66.109.6.76
7 10 ms 19 ms 10 ms ae-0-0.cr0.nyc30.tbone.rr.com [66.109.6.26]
8 18 ms 19 ms 23 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
9 16 ms 16 ms 14 ms ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.167]
10 19 ms 18 ms 16 ms 66.109.9.163
11 26 ms 31 ms 36 ms ae2-p161.msr1.re1.yahoo.com [216.115.108.67]
12 43 ms 37 ms 37 ms ge-1-43.bas-a2.re3.yahoo.com [66.196.112.205]
13 36 ms 44 ms 37 ms f1.www.vip.re1.yahoo.com [69.147.76.15]
Trace complete.
C:\Users\daddy>7:32PM
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\daddy>tracert www.yahoo.com
Tracing route to www.yahoo-ht3.akadns.net [69.147.76.15]
over a maximum of 30 hops:
1 8 ms 9 ms 8 ms x.x.x.x
2 14 ms 20 ms 10 ms gig-0-3-nycmnys-ubr6.nyc.rr.com [24.29.100.50]
3 9 ms 18 ms 10 ms gig-4-1-nycmnys-rtr2.nyc.rr.com [24.29.100.53]
4 11 ms 12 ms 12 ms pos-1-1-nycmnya-rtr2.nyc.rr.com [24.29.130.58]
5 105 ms 101 ms 106 ms tenge-3-0-0-nycsnyoo-rtr1.nyc.rr.com [24.29.119.
114]
6 115 ms 89 ms 90 ms 66.109.6.76
7 119 ms 110 ms 110 ms ae-0-0.cr0.nyc30.tbone.rr.com [66.109.6.26]
8 103 ms 123 ms 97 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
9 103 ms 120 ms 143 ms ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.167]
10 136 ms 130 ms 125 ms 66.109.9.163
11 104 ms 110 ms 129 ms ae2-p161.msr1.re1.yahoo.com [216.115.108.67]
12 152 ms 152 ms 154 ms ge-1-42.bas-a2.re3.yahoo.com [66.196.112.203]
13 132 ms 132 ms 131 ms f1.www.vip.re1.yahoo.com [69.147.76.15]
Trace complete.
C:\Users\daddy>8:46PM The start of the problem begins!
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\daddy>tracert www.yahoo.com
Tracing route to www.yahoo-ht3.akadns.net [69.147.76.15]
over a maximum of 30 hops:
1 10 ms 7 ms 6 ms x.x.x.x
2 11 ms 8 ms 10 ms gig-0-3-nycmnys-ubr6.nyc.rr.com [24.29.100.50]
3 7 ms 9 ms 8 ms gig-4-1-nycmnys-rtr2.nyc.rr.com [24.29.100.53]
4 14 ms 9 ms 8 ms pos-1-1-nycmnya-rtr2.nyc.rr.com [24.29.130.58]
5 195 ms 238 ms 236 ms tenge-3-0-0-nycsnyoo-rtr1.nyc.rr.com [24.29.119.
114]
6 234 ms 205 ms 201 ms 66.109.6.76
7 228 ms 233 ms 211 ms ae-0-0.cr0.nyc30.tbone.rr.com [66.109.6.26]
8 225 ms 204 ms 239 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
9 243 ms 243 ms 212 ms ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.167]
10 234 ms 222 ms 276 ms 66.109.9.163
11 253 ms 228 ms 246 ms ae2-p161.msr1.re1.yahoo.com [216.115.108.67]
12 282 ms 273 ms 254 ms ge-1-43.bas-a2.re3.yahoo.com [66.196.112.205]
13 236 ms 229 ms 271 ms f1.www.vip.re1.yahoo.com [69.147.76.15]
Trace complete.
C:\Users\daddy>8:55PM
C:\Users\daddy>ping 24.29.119.114
Pinging 24.29.119.114 with 32 bytes of data:
Reply from 24.29.119.114: bytes=32 time=279ms TTL=59
Reply from 24.29.119.114: bytes=32 time=279ms TTL=59
Reply from 24.29.119.114: bytes=32 time=273ms TTL=59
Reply from 24.29.119.114: bytes=32 time=273ms TTL=59
Ping statistics for 24.29.119.114:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 273ms, Maximum = 279ms, Average = 276ms
C:\Users\daddy>ping 24.29.130.58
Pinging 24.29.130.58 with 32 bytes of data:
Reply from 24.29.130.58: bytes=32 time=16ms TTL=251
Reply from 24.29.130.58: bytes=32 time=8ms TTL=251
Reply from 24.29.130.58: bytes=32 time=19ms TTL=251
Reply from 24.29.130.58: bytes=32 time=9ms TTL=251
Ping statistics for 24.29.130.58:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 19ms, Average = 13ms
C:\Users\daddy>
| |
-
|
